abapGit and gCTS for AI-Assisted ABAP: Repositories, Branches and Reviewable Diffs

Keep this: job aid

Git for agent-written ABAP: release checklist

• One package tree per repository; push a reviewed baseline to main before agents start.
• Community abapGit in development systems only, approved by Basis and security; SAP's fork only in BTP ABAP environment and S/4HANA Cloud Public Edition.
• Never pull unread code; a person decides every pull, with a transport.
• Set a global check variant and Block Commit if Code Inspection has Errors.
• Short-lived branch per request; commit comment starts with the request number.
• Pull request template: ticket, what the agent was asked, what a person verified, ATC and ABAP Unit evidence.
• Two approvals for agent changes, one from the package owner; the agent can't merge or approve.
• No release before merge; release managers check the merged pull request before import.
• Treat unpushed differences between CMD and main as findings.
• gCTS: vSID and Z-plus-vSID layer, Development vs Provided roles; SAP Note corrections still need classic CTS.