step-security/Backport GitHub Action
Cherry-picks commits from merged pull requests onto one or more target branches, driven by labels on the source PR.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| github_token | Token with repo scope for opening backport PRs and calling the GitHub API. | yes | — |
| auto_backport_label_prefix | Prefix used to derive the target branch from a label name. A label "backport-to-staging" with prefix "backport-to-" targets the "staging" branch. | no | — |
| repo_fork_owner | GitHub user or organisation that owns the fork where backport branches are created. Falls back to the owner of the current repository when omitted. | no | — |
| copy_source_pr_reviewers | Carry over the reviewers assigned to the original pull request onto every backport pull request that is created. | no | false |
| ignore_error_codes | Comma-separated list of error codes that should not cause the workflow step to fail. Leave empty to treat every error as fatal. | no | merge-conflict-exception,no-branches-exception |
Outputs
no outputs