tibdex/Backporting

Automatically backport PRs to other branches by simply labeling them.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
Runtime
Deprecated runtime
namedescriptionrequireddefault
body_templateLodash template for the backport PR's body. The data properties are: - base: backport PR's base branch - body: original PR's body - mergeCommitSha: SHA of the original PR's merge commit - number: original PR's number Backport <%= mergeCommitSha %> from #<%= number %>.
github_tokenToken for the GitHub API.yes
head_templateLodash template for the backport PR's head branch. The data properties are: - base: backport PR's base branch - number: original PR's number backport-<%= number %>-to-<%= base %>
label_patternThe regular expression pattern that PR labels will be tested on to decide whether the PR should be backported and where. The backport PR's base branch will be extracted from the pattern's required `base` named capturing group. ^backport (?<base>([^ ]+))$
labels_templateLodash template compiling to a JSON array of labels to add to the backport PR. The data properties are: - base: backport PR's base branch - labels: array containing the original PR's labels, excluding those matching `label_pattern`. []
title_templateLodash template for the backport PR's title. The data properties are: - base: backport PR's base branch - number: original PR's number - title: original PR's title [Backport <%= base %>] <%= title %>
namedescription
created_pull_requestsA JSON stringified object mapping the base branch of the created pull requests to their number.