c-ares / c-ares / 28589765051
90%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 177
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 91.725% (+0.02%) from 91.709%
28589765051

push

github

web-flow 
Add comment-driven backport workflow for release branches (#1175)

## Summary

Adds a `Backport` GitHub Actions workflow so maintainers can cherry-pick
a merged pull request onto one or more protected release branches (e.g.
`v1.34`, `v1.33`) by commenting on the PR:

```
/backport <branch> [<branch> ...] [--no-automerge]
```

One backport PR is opened per target branch. Because release branches
are protected, changes are always proposed as a **pull request** against
the release branch — never pushed directly.

## Behavior

- **Trigger:** `/backport` comment on a **merged** PR (works
retroactively on already-merged PRs).
- **Maintainers only:** authorized to users whose repository role is
`maintain` or `admin`; anyone else gets a polite refusal. (Uses the
`role_name` field, since the legacy `permission` field collapses
`maintain`→`write`.)
- **Auth:** mints a **GitHub App token** so backport PRs trigger CI and
work with branch protection.
- **Clean cherry-pick:** the backport PR is opened with **auto-merge
enabled by default**, so GitHub merges it once all *required* status
checks on the target branch pass. Opt out per-invocation with
`--no-automerge`.
- **Conflict:** the conflict markers are committed and a **draft** PR is
opened for manual resolution. Draft PRs are never auto-merged.

Engine is
[`korthout/backport-action`](https://github.com/korthout/backport-action)
(`@v4`), with `experimental: {"conflict_resolution":
"draft_commit_conflicts"}` for the conflict behavior.

## One-time setup required (repo admin)

Documented in `BACKPORTING.md`:

1. A **GitHub App** with *Contents: R/W* and *Pull requests: R/W*,
installed on the repo; secrets `BACKPORT_APP_ID` and
`BACKPORT_APP_PRIVATE_KEY`.
2. **Allow auto-merge** enabled in repository settings.
3. **Branch protection on `v*`** requiring a PR and requiring the CI
status checks (so auto-merge waits for CI instead of merging
immediately).

## Files

- `.github/workflows/backport.yml` — the workflow.
- ... (continued)

23022 of 25099 relevant lines covered (91.72%)

12554.78 hits per line

Jobs
ID Job ID Ran Files Coverage
1 28589765051.1 935
61.09
 GitHub Action Run
Source Files on build 28589765051