Skip to content
Skills Library
Programming · Tool integration

abapgit

/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", "transp

Repository
abap-skills ↗
Licence
MIT
Last repository change
16.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
5
Deprecation

No signals detected. Repository changed on 16.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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", "transp

Triggers from the description

set up abapGitclone a repopush ABAP to gitabapGit branchingabapGit configuration.abapgit.xml
Original author 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", "transp

How it works

  1. Workflow
  2. abapGit Overview
  3. Setup
  4. Core Operations
  5. .abapgit.xml Configuration
  6. Branching Strategy
  7. Transport vs. Git Workflows
  8. CI/CD Integration
  9. Troubleshooting
  10. Output Format
Original SKILL.md headings · 245 lines, 936 words
SKILL.md preview
---
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

| Aspect                | Description                                                       |
| --------------------- | ----------------------------------------------------------------- |
| **What**              | Open-source Git client for ABAP, runs inside the SAP system       |
| **Serialization**     | Converts ABAP objects to file-based format for Git storage        |
| **Deserialization**   | Imports file-based format back into ABAP objects in the system    |
| **Supported Objects** | Classes, interfaces, CDS, function groups, programs, tables, etc. |
| **Installation**      | Via 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
<?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

| Setting           | Values              | Description                                     |
| ----------------- | ------------------- | ----------------------------------------------- |
| `MASTER_LANGUAGE` | `E`, `D`, etc.      | Master language for texts                       |
| `STARTING_FOLDER` | `/src/`             | Root folder for serialized objects              |
| `FOLDER_LOGIC`    | `PREFIX` / `FULL`   | How package hierarchy maps to folders           |
| `IGNORE`          | File patterns       | Files to exclude from deserialization           |
| `REQUIREMENTS`    | Software components | Dependencies 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

| Aspect                  | Transport-Based     | Git-Based (abapGit)                      |
| ----------------------- | ------------------- | ---------------------------------------- |
| **Versioning**          | Transport requests  | Git commits with full history            |
| **Collaboration**       | Transport of copies | Branches, pull requests, code review     |
| **Rollback**            | Difficult           | `git revert` or checkout previous commit |
| **CI/CD**               | Limited             | Full integration with pipelines          |
| **Multi-system**        | Transport routes    | Clone/pull to each system                |
| **Conflict resolution** | Manual              | Git merge tools                          |

### Hybrid Approach

Many teams use abapGit for version control while retaining transports for deployment:

1. Develop in DEV system
2. Commit changes to Git (abapGit push)
3. Use transport requests to move to QAS/PRD
4. Git serves as source of truth and backup

## CI/CD Integration

### abaplint in CI Pipeline

```yaml
# .github/workflows/abaplint.yml
name: abaplint
on: [push, pull_request]
jobs:
  abaplint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: niclas-timm/abaplint-action@main
```

### abaplint.json Configuration

```json
{
  "global": {
    "files": "/src/**/*.*"
  },
  "syntax": {
    "version": "Cloud",
    "errorNamespace": "^(Z|Y|LCL_|LIF_)"
  },
  "rules": {
    "description": "ABAP lint configuration"
  }
}
```

## Troubleshooting

| Issue                      | Solution                                     |
| -------------------------- | -------------------------------------------- |
| SSL handshake error        | Import SSL certificates via `STRUST`         |
| Authorization error        | Check `S_DEVELOP` authorization object       |
| Object locked by transport | Release or remove transport lock             |
| Serialization error        | Check object type support in abapGit         |
| Namespace conflicts        | Ensure unique naming conventions             |
| Large repository slow      | Use shallow clone or split into sub-packages |

## Output Format

When helping with abapGit topics, structure responses as:

```markdown
## abapGit Guidance

### Context

- Environment: [On-premise / BTP / gCTS]
- Operation: [Clone / Push / Pull / Setup]

### Steps

[Step-by-step instructions]

### Configuration

[Relevant .abapgit.xml or abaplint settings]
```

## References

- abapGit Documentation: https://docs.abapgit.org/
- abapGit GitHub: https://github.com/abapGit/abapGit
- abaplint: https://abaplint.org/

## Related Skills

- **abap**: Use for abaplint integration with abapGit repositories
- **btp-abap-environment**: Use for abapGit setup in BTP ABAP Environment
- **abap-cloud**: Use for ensuring abapGit repositories are ABAP Cloud compliant

Versions

The database has no other skills named abapgit.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version eecfe50aff02 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100setup-abap-mirror
    Create a local abapGit-style mirror of an SAP package or object set so you can git-diff and search locally without round-tripping every read. Use when asked to "mirror this package locally", "set up local ABAP files", "create an abapGit-style mirror", or "pull these objects to…
  • 90abap-adt-mcp
    Develop ABAP through the abap-adt-mcp MCP server (server key `abap-adt-mcp`): read, search, edit, activate, test, check and transport ABAP objects on S/4HANA Cloud and on-prem systems. Use whenever a task touches ABAP code, CDS, RAP, transports, ATC, unit tests, dumps or abapGit…
  • 91abap-check
    The catalogue of ABAP problems a green CI does not catch - abapGit round-trip and import failures (BOM, line endings, trailing whitespace, EOF newline, 255-character lines, metadata sidecars for CLAS and for DDLS/BDEF/TABL), activation errors abaplint does not model…
  • 100clean-abap
    Use when writing, generating, or modifying ABAP code, or when reviewing / code-reviewing ABAP objects (classes, function modules, programs, includes, interfaces, transports). Applies SAP's Clean ABAP style guide. Triggers on ABAP, SAP, .abap source, SE80/SE24/SE37/ADT objects, and transport reviews.
  • 100abap
    Comprehensive ABAP code quality checking using abaplint (automated static analysis) and Clean ABAP principles (manual code review). Use when users ask to check, lint, validate, review, or analyze ABAP code for syntax errors, clean code compliance, code quality, best practices,…
  • 90abap-code-review
    Use when asked to review ABAP - a diff, a transport request or task, a pull request, a class / function module / program, or "check my ABAP before release". Collects the change and its goal, checks facts on the system, runs an independent reviewer pass, and reports findings…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.