#ABAP#abapGit#git

Moving code between systems with abapGit, no STMS involved

abapGit can carry your development from one system to another without a single transport request. It's powerful and dangerous in equal measure. Here's how it works, when it makes sense and where you should NOT use it.

May 14, 2026

#ABAP#abapGit#git

abapGit: what it is and why you should finally version your ABAP

abapGit is a Git client written in ABAP that runs inside the system itself. It isn't a community novelty: it's how you free your code from the tyranny of transports and put it under real version control.

May 12, 2026

#ABAP#abapGit#git

Online vs offline repos in abapGit: when it connects and when it doesn't

abapGit has two repository modes: online, tied to a remote GitHub, and offline, a ZIP you carry by hand. They aren't the same and don't serve the same purpose. Choosing wrong costs you a whole workflow.

May 9, 2026

#ABAP#abapGit#git

abapGit in practice: best practices and the mistakes you will absolutely hit

Unsupported objects, phantom dependencies, expired tokens, a badly set master language. abapGit works beautifully until one of these bites you. Here's the list of what goes wrong and how to avoid it.

May 8, 2026

#ABAP#abapGit#git

The abapGit workflow: staging, commit, push, pull and branches without drama

The daily abapGit cycle isn't magic: it's git add, git commit and git push translated into ADT. Here's the real flow, with the Staging view, commit messages that actually help, and why branches save you.

May 6, 2026

#ABAP#abapGit#git

The .abapgit.xml and package mapping: the piece almost nobody looks at

That small file at the repo root decides how ABAP packages map to folders and back. Folder logic FULL or PREFIX, master language, starting folder. Here's what it does and why it matters.

May 4, 2026

← All posts