Git for TIA Portal & PLC code

Git for TIA Portal means versioning PLC code like software: commit changes, view diffs, manage branches and sync with a remote. AnyAutomation Studio brings a built-in Git source control straight into the IDE — without leaving the editor.

How does Git work in AnyAutomation Studio?

Through the source control view you stage and commit changes to blocks and project files, view diffs, manage branches and push, pull or sync with any Git remote — GitLab, GitHub, Azure DevOps or self-hosted. Because SCL unit test suites are plain-text JSON files next to the project, you version tests and code together. Details in the Git client documentation.

How does it fit Openness, tests and CI/CD?

Git is the basis of the end-to-end flow: AI generates → Openness imports → unit tests verify → Git and CI/CD track every change. Dedicated tools like VCI or octoplant cover project archiving more broadly; Studio focuses on code- and test-level versioning right inside the engineering IDE.

Frequently asked questions

Can you version TIA Portal projects with Git?

Yes. AnyAutomation Studio ships with built-in Git version control that lets you stage, commit, diff blocks and project files and sync with a remote.

How does Git work in AnyAutomation Studio?

Through a source control view in the IDE: stage and commit changes, view diffs, manage branches and push, pull and sync — the familiar Git workflow for PLC code.

What is the difference from VCI or octoplant?

VCI and octoplant target broad project archiving and management. AnyAutomation Studio focuses on code- and test-level Git versioning right inside the engineering IDE, tightly tied to AI generation and unit tests.

Can I version SCL unit test suites with Git?

Yes. Test suites are plain-text JSON files next to your project file and can be staged, committed, diffed and reviewed like any other code.

Does it work with GitLab and GitHub?

Yes. You can sync with any Git remote — GitLab, GitHub, Azure DevOps or self-hosted.