Publish to Git
Send the design history of your iFlows to a GitHub repository, one commit per batch of revisions.
Audit can publish each design revision to a GitHub repository, so the history lives in the tools your developers already use.
Set it up
Section titled “Set it up”- An admin opens Settings → Audit → Git repositories and adds the repository, with a personal access token. Required permissions in that screen lists what the token needs.
- Test connection must succeed. A repository that was saved but never tested does not receive anything.
- Turn on publishing (Publish Audit changes to the connected repositories).
The token is stored encrypted.
What gets published
Section titled “What gets published”- Revisions are published after each sync, oldest first, so the commits follow the order of the changes.
- Each iFlow has its own folder, and the folder always mirrors the latest published revision. A file removed from the design is removed from the repository in the next commit.
- Removing an iFlow from SAP does not delete its folder.
- Only design revisions are published. Parameters and deployment stay in Integration Mapper.