Version control
Keeping a history of changes to code or configuration files so versions can be compared, reviewed, and restored when needed.
On this page
Source content checked . English translation published 2026-10-27.
In business automation
In automation, version control helps show what changed before a failure and who reviewed it. Decide what belongs in a file and what should remain as a setting or secret in the runtime environment.
Examples
These examples illustrate a possible workflow. Adapt the connections and rules to your own systems.
Business process example
A team changes a lead assignment rule and saves the change with an explanation and checks. If requests start going to the wrong team, they can compare the rule with the previous version instead of guessing what was edited.
Relevant tools
- GitHub Actions
- Can check changes saved in a Git repository. Version control itself is managed in the repository, not in the checking workflow.
What to check
- Do not store secrets in code history. Removing a key from the latest version does not remove it from the full history.