actions-marketplace-validations/Backporting GitHub Action
GitHub action providing an automated way to backport pull requests from one branch to another
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Mar 30, 2026
- License
- MIT
Pinned Snippet
uses: actions-marketplace-validations/lampajr_backporting@a618d55f32ad3d868922e949bec44cd73dd9bd1d # no releases — HEAD as of 2026-07-13tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| pull-request | URL of the pull request to backport, e.g., "https://github.com/kiegroup/git-backporting/pull/1" | no | — |
| target-branch | Comma separated list of branches where the pull request must be backported to | no | — |
| target-branch-pattern | Regular expression pattern to extract target branch(es) from pr labels. The branches will be extracted from the pattern's required `target` named capturing group, for instance "^backport (?<target>([^ ]+))$" | no | — |
| config-file | Path to a file containing the json configuration for this tool, the object must match the Args interface | no | — |
| dry-run | If enabled the tool does not create any pull request nor push anything remotely | no | false |
| auth | GITHUB_TOKEN or a `repo` scoped Personal Access Token (PAT), if not provided will look for existing env variables like GITHUB_TOKEN | no | ${{ github.token }} |
| git-client | Git client type <github|gitlab|codeberg>, if not set it is infered from pull-request | no | — |
| git-user | Local git user name | no | GitHub |
| git-email | Local git user email | no | noreply@github.com |
| title | Backporting PR title. Default is the original PR title prefixed by the target branch | no | — |
| body-prefix | Backporting PR body prefix. Default is `Backport: <original-pr-link>` | no | — |
| body | Backporting PR body. Default is the original PR body | no | — |
| bp-branch-name | Comma separated list of backporting PR branch names. Default is auto-generated from commit and target branches | no | — |
| reviewers | Comma separated list of reviewers for the backporting pull request | no | — |
| assignees | Comma separated list of reviewers for the backporting pull request | no | — |
| no-inherit-reviewers | Considered only if reviewers is empty, if true keep reviewers as empty list, otherwise inherit from original pull request | no | false |
| labels | Comma separated list of labels to be assigned to the backported pull request | no | — |
| inherit-labels | If true the backported pull request will inherit labels from the original one | no | false |
| no-squash | Backport all commits found in the pull request. The default behavior is to only backport the first commit that was merged in the base branch. | no | — |
| auto-no-squash | If the pull request was merged or is open, backport all commits. If the pull request commits were squashed, backport the squashed commit. | no | — |
| strategy | Cherry-pick merge strategy | no | recursive |
| strategy-option | Cherry-pick merge strategy option | no | theirs |
| cherry-pick-options | Additional cherry-pick options | no | — |
| comments | Semicolon separated list of additional comments to be posted to the backported pull request | no | — |
| enable-err-notification | If true, enable the error notification as comment on the original pull request | no | false |
Outputs
no outputs