{"ref":"artifact:catafeidi-abap-transport-review","page":"/artifacts/catafeidi-abap-transport-review","json":"/artifacts/catafeidi-abap-transport-review.json","generated":"2026-11-15","drafted_with_ai":true,"entity":{"id":"catafeidi-abap-transport-review","name":"abap-transport-review","artifact_type":"app","ecosystem":"abap","flavors":[{"key":"standard-abap","source":{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, Supported systems","checked":"2026-10-12","quote":"The tools are classic ABAP on an on-premise or private-cloud system. They use the classic transport check (BAdI `CTS_REQUEST_CHECK`), background jobs, report variants and the cluster table `INDX`, none of which is part of ABAP Cloud."}}],"domain":"developer-experience","secondary_domains":["operations-and-runtime"],"origin_ring":"independent","description":{"one_line":"A release check inside the ABAP system that turns every transport task into a GitHub pull request and refuses to release the request until a colleague has approved it.","short":"Transport release check gated by GitHub pull request approval","what_it_solves":"A classic transport request records which objects moved and who released them, not what changed inside them or who read it before it left. This project puts that record on GitHub: releasing a task commits its objects to the branch `review/<request>` through [abapGit](artifact:abapgit-abapgit) and opens a pull request under the releasing developer's own GitHub account, and the request cannot be released until somebody else has approved that pull request, which the release then squashes and merges. What a transport carries that abapGit cannot write — table rows, report variants, authorization profiles, old OTR texts, ALV layouts and SAP Note entries — travels in the same commit as JSON under `content/`, and the report `ZTR_APPLY_CONTENT` applies those files in another system. All of it is local objects of the development system: a BAdI implementation on `CTS_REQUEST_CHECK`, background jobs, and the reports `ZTR_SETUP`, `ZTR_GITHUB_LOGIN` and `ZTR_PUSH_TRANSPORT`. It stops at the review: the transport request still moves between systems the way the landscape moves it today, and git holds the reviewed copy rather than deploying it.","when_not_to_use":"Not below SAP_BASIS 7.40 SP08, and not on [SAP S/4HANA Cloud Public Edition](external:sap-s4hana-cloud-public-edition) or [the SAP BTP ABAP environment](artifact:btp-abap-environment), where the classic transport check, the report and job calls and the cluster table `INDX` it rests on do not exist and the maintainer names gCTS as the answer instead. Only on a development system where every developer is trusted: each developer's GitHub token is kept in a cluster table encrypted with a key held in the same table, so anybody who can run ABAP on that system can read both, and the separation between author and reviewer holds only as far as that trust does. Not where the gate has to be unconditional — `#NOREVIEW` in a request's short text skips the check for that request, `ZTR_DISABLED` switches it off for a system, a check that cannot reach GitHub lets the release go on, and nothing checks who writes the marker.","to_build_on_it":"The work is in classes without a screen, `ZCL_TR_SETUP` and `ZCL_TR_AUTH`, which is what the maintainer names as the way a front end could be put on top later; the two ADT console classes in the sub-package `$ZTR_REVIEW_CONSOLE` already drive the check and the login as text and can be started from a script or through the ADT HTTP interface. The roadmap states what is not there, as ideas without dates: an ABAP Cloud answer built on gCTS and a GitHub branch rule rather than a port of this code, a first import that publishes the last released version of objects already in an open task so the first pull request shows a diff, and more unit tests for the push report and the release check. A change goes in as a fork and a pull request that a maintainer reviews, with the [abaplint](artifact:abaplint-abaplint) check `abaplint 7.40` running on it; the licence is MIT."},"links":{"repo":"https://github.com/catafeidi/abap-transport-review","issues":"https://github.com/catafeidi/abap-transport-review/issues"},"type_properties":{"distribution":{"value":["abapgit"],"sources":[{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, Prerequisites","checked":"2026-10-12","quote":"abapGit **developer version** on the system (`ZABAPGIT`, package `$ABAPGIT`)"}]},"placement":{"value":"in-host","sources":[{"url":"https://github.com/catafeidi/abap-transport-review","title":"abap-transport-review — README","checked":"2026-10-18","quote":"Everything runs inside the SAP development system, in ABAP, on top of [abapGit](https://github.com/abapGit/abapGit)."}]}},"identity":{"license":"MIT"},"source_available":true,"provides":[{"capability":"capability:abap-code-review","what_it_does":"Makes the review a gate on the release: releasing a task commits its objects to `review/<request>` and opens a pull request under the releasing developer's GitHub account, and the release of the request is refused until that pull request is approved by somebody other than its author. Rework is a new task in the same request, which adds a commit to the same pull request and dismisses the approvals given before, so the record on GitHub carries every round — the diff, who commented, who approved and when — and the release check refuses the request if an object changed after the last push, pushing it for review instead.","sources":[{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, opening","checked":"2026-10-12","quote":"Releasing a task commits its objects to a review branch and opens a pull request. A request cannot be released until a colleague has approved that pull request, and the release of the request merges it."},{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, Why use it","checked":"2026-10-12","quote":"Every task becomes a pull request under the developer's own GitHub account, and the request cannot be released until its pull request is approved by somebody else: GitHub does not count the approval of the author."},{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, How it works, step 4","checked":"2026-10-12","quote":"A new commit dismisses the approvals given before (with the ruleset of this project), so the reviewer looks again."},{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, How it works, step 5","checked":"2026-10-12","quote":"If it is not approved, or an object changed after the last push, the release is refused with the reason, and a changed object is pushed to the same pull request so that it can be reviewed again."}]},{"capability":"capability:abap-source-control","what_it_does":"Covers the entries of a transport that [abapGit](artifact:abapgit-abapgit) does not serialise. Table rows (`TABU`, `TDAT`, `VDAT`, `CDAT`), report variants, authorization profiles, old OTR texts, ALV layouts and SAP Note entries are written as JSON under `content/` in the same commit as the objects under `src/`, and the report `ZTR_APPLY_CONTENT` reads them back into another system, recording the keys on a transport request first and then writing the rows. What neither abapGit nor `ZCL_TR_CONTENT` can write is listed on the pull request under \"Not in Git\", and the setting `ZTR_REQUIRE_COMPLETE` turns that listing into a refused release.","sources":[{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, Objects that abapGit cannot write","checked":"2026-10-12","quote":"abapGit turns repository objects (classes, interfaces, tables, programs and so on) into files under `src/`. A transport carries more than that: table rows, report variants, authorization profiles, old OTR texts, ALV layouts and SAP Note entries. This project writes them as JSON files under `content/`, in the same commit and the same pull request as the objects, so a reviewer sees them too."},{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, Bringing it into another system","checked":"2026-10-12","quote":"abapGit pulls only `src/`. The report `ZTR_APPLY_CONTENT` does the rest:"},{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, Bringing it into another system, step 3","checked":"2026-10-12","quote":"The keys are recorded in the request first, then the rows are written. The request travels on like any other."},{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, the entries table, Anything else","checked":"2026-10-12","quote":"The pull request lists it under \"Not in Git\" and so does the job log, so the reviewer checks it on the system. This is not an error by default. With the setting `ZTR_REQUIRE_COMPLETE` the release of such a request is refused with an error"}]}],"requires":[{"ref":"artifact:abapgit-abapgit","for":"The tools call abapGit's own classes to serialise and push the objects of a task, and the repository is installed into the system with it; the README states the standalone report is not enough.","requirement":"required","sources":[{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, Prerequisites","checked":"2026-10-12","quote":"abapGit **developer version** on the system (`ZABAPGIT`, package `$ABAPGIT`)"},{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, Prerequisites","checked":"2026-10-12","quote":"the tools call its classes; the standalone report is not enough"}]},{"ref":"external:github","for":"The pull requests, the reviews and the branch ruleset that keeps the base branch to what has been released all live on GitHub, and each developer's token is issued by a GitHub App installed on the repositories.","requirement":"required","sources":[{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, opening","checked":"2026-10-12","quote":"This project connects the SAP transport system with GitHub pull requests."},{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, Prerequisites","checked":"2026-10-12","quote":"A GitHub App installed on those repositories"},{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, Prerequisites","checked":"2026-10-12","quote":"the token of each developer is issued by it and only sees repositories the app is installed on"}]},{"ref":"artifact:abaplint-abaplint","for":"an optional check of the pull request's syntax and the Clean ABAP rules before a colleague reviews it","requirement":"conditional","condition":"the abaplint GitHub Actions check is turned on for the repository","basis":"binding","role":"quality-check","sources":[{"url":"https://github.com/catafeidi/abap-transport-review","title":"abap-transport-review README","checked":"2026-10-18","quote":"abaplint can run on GitHub on every pull request (the syntax of your target release and the Clean ABAP rules; the workflows are in `github-templates/`)"}]}],"connects":[{"ref":"external:github","kind":"data","protocols":["http"],"direction":"outbound","for":"Commits the objects of a released task to the branch `review/<request>`, opens the pull request for it, compares the objects of the request with that branch when the request is released, and squashes and merges the pull request into the base branch. The push, the pull request and the merge run as background jobs.","sources":[{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, Prerequisites","checked":"2026-10-12","quote":"Outbound HTTPS from the SAP system to `github.com` and `api.github.com` (port 443)"},{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, How it works, step 6","checked":"2026-10-12","quote":"When the request is released in SAP, a job squashes and merges the pull request into the base branch, through the GitHub App."}]},{"ref":"external:github","kind":"authentication","protocols":["http"],"direction":"outbound","for":"Logs each developer in once through the device flow of the GitHub App and keeps the resulting token per SAP user, encrypted, so that every commit, pull request and merge is made under that developer's own account.","sources":[{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, The flow","checked":"2026-10-12","quote":"Each developer logs in once (GitHub device flow); the token is kept per SAP user, encrypted."},{"url":"https://github.com/catafeidi/abap-transport-review","title":"catafeidi/abap-transport-review — README, The flow","checked":"2026-10-12","quote":"Everything on GitHub happens under the account of the developer who releases. There is no shared technical user and no token in SM59."}]}],"maintainers":["actor:catafeidi"],"history":[{"date":"2026-10-12","field":"entry","from":null,"to":"created","reason":"Entered by intake from the repository README and the repository's own facts. Placed on the ABAP door in the standard-abap flavor only, because the README states the tools are classic ABAP using the CTS_REQUEST_CHECK BAdI, background jobs and the cluster table INDX, \"none of which is part of ABAP Cloud\"."}],"drafted_with_ai":true,"provenance":{"discovered_via":[{"source":"source:curator"}],"first_seen":"2026-10-12"},"contributors":["actor:catafeidi"]},"effective_normative_relations":[],"readings":{"liveness":[{"label":"Maintenance","tier":"unknown","evidence":"no release data"},{"label":"Continuity","tier":"fair","evidence":"one contributor, personally owned"},{"label":"Repository","tier":"good","evidence":"pushed 2026-10, not archived"}],"compatibility":[{"label":"Declared for","tier":"good","evidence":"SAP_BASIS 740 and up, in its abaplint config: includes every maintained line to 816"},{"label":"Survived majors","tier":"unknown","evidence":"not read on ABAP: its lines run side by side"},{"label":"Maintainer's CI","tier":"fair","evidence":"workflows present, no completed run on the default branch"}],"practice":[{"label":"Tests","tier":"good","evidence":"1 test file"},{"label":"Docs","tier":"good","evidence":"docs/ with 14 pages, README 37 KB"},{"label":"Changelog","tier":"fair","evidence":"none in the repo"}],"reach":[{"value":null,"unit":"installs/week"},{"value":1,"unit":"watching"}]},"signals":{"crawled_at":"2026-11-13","npm":"not published under this name","stars":1,"forks":0,"open_issues":0,"archived":false,"pushed_at":"2026-10-28","license_spdx":"MIT","org_owned":false,"default_branch":"master","created_at":"2026-10-11T11:57:28Z","open_prs":0,"tree_truncated":false,"test_files":1,"workflows":1,"other_ci":false,"readme_bytes":38088,"docs_files":14,"changelog":false,"license_file":true,"dts_files":0,"first_commit":"2026-10-11","last_commit":"2026-10-28","commits":22,"contributors":1,"readme_path":"README.md","readme_sha":"d457564d3aca0b8115f4800914ca43058364e268","repo_read":"2026-11-13","language":"ABAP","abap_syntax":{"repo":"catafeidi/abap-transport-review","file":"abaplint.json","url":"https://github.com/catafeidi/abap-transport-review/blob/HEAD/abaplint.json","version":"v740sp08","floor":"740","checked":"2026-11-15"}},"edges":{"maintainers":[{"ref":"actor:catafeidi","name":"catafeidi","json":"/actors/catafeidi.json"}],"contributors":[{"ref":"actor:catafeidi","name":"catafeidi","json":"/actors/catafeidi.json"}],"explained_by":[],"alternative_to_this":[],"needed_by":[],"available_via":[],"parts":[],"add_ons":[],"answered_through_parts":[]}}