Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Development

abapgit

Help with abapGit workflows including repository setup, cloning, serialization, branching strategies, transport-vs-git workflows, CI/CD integration, and .abapgit.xml configuration. Use when users ask about abapGit, git for ABAP, ABAP version control, abapGit clone, abapGit pull, abapGit push, branching strategy for ABAP, abapGit configuration, serialization, deserialization, transport vs git, gCTS, abapGit CI/CD, or managing ABAP code in git repositories. Triggers include "set up abapGit", "clone a repo", "push ABAP to git", "abapGit branching", "abapGit configuration", ".abapgit.xml", "transport vs git", or "CI/CD for ABAP".

likweitan · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add likweitan/abap-skills --skill abapgit

About this skill


name: abapgit description: Help with abapGit workflows including repository setup, cloning, serialization, branching strategies, transport-vs-git workflows, CI/CD integration, and .abapgit.xml configuration. Use when users ask about abapGit, git for ABAP, ABAP version control, abapGit clone, abapGit pull, abapGit push, branching strategy for ABAP, abapGit configuration, serialization, deserialization, transport vs git, gCTS, abapGit CI/CD, or managing ABAP code in git repositories. Triggers include "set up abapGit", "clone a repo", "push ABAP to git", "abapGit branching", "abapGit configuration", ".abapgit.xml", "transport vs git", or "CI/CD for ABAP".

abapGit Workflows

Guide for managing ABAP development objects in Git repositories using abapGit.

Workflow

  1. Determine the user's goal:

    • Setting up abapGit for the first time
    • Cloning an existing repository
    • Pushing ABAP code to a Git repository
    • Configuring branching or transport strategies
    • Setting up CI/CD pipelines for ABAP
    • Troubleshooting abapGit issues
  2. Identify the environment:

    • On-premise SAP system with abapGit standalone
    • SAP BTP ABAP Environment (abapGit integration in ADT)
    • gCTS (Git-enabled Change and Transport System)
  3. Guide implementation with best practices for ABAP-specific Git workflows

abapGit Overview

AspectDescription
WhatOpen-source Git client for ABAP, runs inside the SAP system
SerializationConverts ABAP objects to file-based format for Git storage
DeserializationImports file-based format back into ABAP objects in the system
Supported ObjectsClasses, interfaces, CDS, function groups, programs, tables, etc.
InstallationVia abapGit standalone report or Eclipse plugin

Setup

Installing abapGit Standalone (On-Premise)

  1. Create report ZABAPGIT_STANDALONE or ZABAPGIT_FULL
  2. Download latest version from https://raw.githubusercontent.com/abapGit/build/main/zabapgit_standalone.prog.abap
  3. Copy content into the report and activate
  4. Run the report via SE38 or transaction ZABAPGIT

abapGit in ADT (BTP ABAP Environment)

  1. In ADT: Window → Show View → Other → abapGit Repositories
  2. Link repository using HTTPS URL
  3. Requires communication arrangement for Git service

SSL Certificates

  • Download GitHub/GitLab root certificates
  • Import via STRUST (transaction) → SSL Client (Anonymous) or (Standard)
  • Required for HTTPS connections to Git providers

Core Operations

Clone a Repository

1. Open abapGit (standalone or ADT)
2. Click "+ Clone" / "Link abapGit Repository"
3. Enter repository URL (HTTPS)
4. Select target package (create if needed)
5. Select branch (default: main)
6. Pull objects into the system

Push Changes to Git

1. Stage changed objects (select what to include)
2. Write a meaningful commit message
3. Push to remote branch
4. Resolve conflicts if any

Pull Updates from Git

1. Open the repository in abapGit
2. Click "Pull"
3. Review incoming changes
4. Activate pulled objects

.abapgit.xml Configuration

The .abapgit.xml file in the repository root controls serialization settings:

<?xml version="1.0" encoding="utf-8"?>
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
 <asx:values>
  <DATA>
   <MASTER_LANGUAGE>E</MASTER_LANGUAGE>
   <STARTING_FOLDER>/src/</STARTING_FOLDER>
   <FOLDER_LOGIC>PREFIX</FOLDER_LOGIC>
   <IGNORE>
    <item>/.gitignore</item>
    <item>/LICENSE</item>
    <item>/README.md</item>
    <item>/package.json</item>
    <item>/.travis.yml</item>
   </IGNORE>
   <REQUIREMENTS/>
  </DATA>
 </asx:values>
</asx:abap>

Key Settings

SettingValuesDescription
MASTER_LANGUAGEE, D, etc.Master language for texts
STARTING_FOLDER/src/Root folder for serialized objects
FOLDER_LOGICPREFIX / FULLHow package hierarchy maps to folders
IGNOREFile patternsFiles to exclude from deserialization
REQUIREMENTSSoftware componentsDependencies that must be present before import

Folder Logic

  • PREFIX: Package name prefix is removed. Z_PKG_SUB under Z_PKG → sub/ folder
  • FULL: Full package name becomes folder. Z_PKG_SUB → z_pkg_sub/

Branching Strategy

Recommended: Trunk-Based for ABAP

main (production-ready)
  └── feature/add-validation
  └── feature/new-report
  └── bugfix/fix-calculation
  • Keep main branch stable and deployable
  • Create short-lived feature branches
  • Merge via pull requests with code review
  • One SAP system per branch for development

Transport-Based Strategy

DEV system ←→ feature branches
QAS system ←→ release branch
PRD system ←  main branch (tags for releases)

Transport vs. Git Workflows

AspectTransport-BasedGit-Based (abapGit)
VersioningTransport requestsGit commits with full history
CollaborationTransport of copiesBranches, pull requests, code review
RollbackDifficultgit revert or checkout previous commit
CI/CDLimitedFull integration with pipelines
Multi-systemTransport routesClone/pull to each system
Conflict resolutionManu
Read the complete source ↗