Version TIA Portal with Git
PLC code is code — and it belongs under version control. With the built-in Git source control in AnyAutomation Studio you treat your TIA Portal project like any other software repository.
Why Git for PLC code?
Without version control, "who changed what, and when" is hard to answer. Git gives you history, diffs, branches and reviews — the traceability automation often lacks.
The workflow
The familiar cycle runs through the source control view:
- Stage — select changed blocks and project files.
- Commit — capture them with a meaningful message.
- Diff — review what changed line by line before committing.
- Branch & merge — develop features in isolation, then merge.
- Push / pull / sync — with GitLab, GitHub, Azure DevOps or self-hosted.
Version the tests too
The real leverage: SCL unit test suites are plain-text JSON files next to the project. They travel in the same commit — code and its tests stay together, diffable and reviewable.
On the way to the pipeline
Once the code is in Git, the step to CI/CD is small: the pipeline checks out, runs the unit tests and reports back. More detail in the Git client documentation and on the Git for TIA Portal page.