abapGit Pull
sap_abapgit_pullPull changes from a remote Git repository into ABAP objects via abapGit, overwriting local versions. Select the repo by name, URL, or key, and optionally specify a branch or transport request.
Instructions
Pull changes from a remote git repository using abapGit API. WARNING: overwrites local ABAP objects. Select the repository by repo (name/URL) or by key (from sap_abapgit_list_repos), not both. If a transport is required the error says so: retry with trkorr=... If 'status unknown', the pull may have run: check the last pull time before retrying. Optional branch switches the repository to that branch persistently (kept only if the pull succeeds) and clears a commit pin.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "sap_abapgit_pull"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | abapGit repository key, 1 to 12 digits (zero-padded to 12), as shown by `sap_abapgit_list_repos` (online repositories only). Use it instead of `repo` when name or URL is not unique: abapGit allows two repositories with the same name or URL, the key is the only unique identifier. Exactly one of `repo` and `key`. Unlike the `key` filter of `sap_abapgit_list_repos`, it is not stripped: surrounding blanks are rejected. Needs a report version with P_KEY. | |
| pat | No | GitHub Personal Access Token (optional for public repos). Falls back to ABAPGIT_PAT env var, then GITHUB_PAT. | |
| repo | No | abapGit repository name (hyphens allowed, e.g. MY-PROJECT-ABAP) or its full https URL. Matched exactly by the report, not a pattern. Exactly one of `repo` and `key`; omit the unused one, do not pass an empty string. | |
| branch | No | Branch to pull (optional): `main`, `feature/x` or `refs/heads/x`. Without it the repository is pulled on its selected branch. SIDE EFFECT: switches the registered repository to this branch persistently (like a branch switch in the abapGit UI) and clears a commit pin; the switch is kept only if the pull succeeds and is restored on failure. The result's `branch` echoes the full branch the repository is on; `sap_abapgit_list_repos` shows it too. | |
| trkorr | No | Transport request (optional, but error if SAP requires it). If pull fails with "Transport required", retry with trkorr. | |
| session | No | Session ID (e.g., "s1", "s2"). None uses primary session. | |
| agent_id | No | Agent identifier for binding check. Optional. | |
| username | No | GitHub username (optional for public repos) |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | Error message if failed | |
| action | Yes | Action type | |
| branch | No | Full branch (e.g. refs/heads/main) the repository is on after a pull with a `branch` argument, as echoed by the report; None without a `branch` argument or when the pull failed | |
| message | No | Status message | |
| success | Yes | Whether the action succeeded | |
| repo_name | Yes | Repository name; for a pull by key the name from the status text when reliable, else `key <12 digits>` | |
| executed_at | Yes | When the action was executed | |
| clicked_action | No | The action button text that was clicked (e.g., 'Pull', 'Stage') |