CI: auto-update open PR branches (open-source autoupdate Action) #20

Closed
opened 2026-07-02 18:17:54 +00:00 by JMR-dev · 0 comments
JMR-dev commented 2026-07-02 18:17:54 +00:00 (Migrated from github.com)

Context

With multiple PRs in flight through the loop, branches drift behind main as PRs merge. Add the open-source chinthakagodawita/autoupdate GitHub Action to automatically keep open PR branches up to date with main as they progress.

Scope

  • Add .github/workflows/autoupdate.yml triggered on push to main.
  • Use chinthakagodawita/autoupdate, pinned to a released version (prefer a commit SHA for supply-chain safety).
  • Auth via the default GITHUB_TOKEN; minimal permissions (contents: write, pull-requests: write); PR_FILTER: all.
  • Document the known trade-off that GITHUB_TOKEN-initiated updates do not re-trigger downstream workflow runs.

Acceptance criteria

  • On a merge to main, other open PRs targeting main get their branches updated automatically.
  • Workflow YAML is valid.

Notes

Requested mid-flight by maintainer. Complements the CI ticket (#3); kept as a separate workflow file since it has a different trigger (push: main) and concern.

## Context With multiple PRs in flight through the loop, branches drift behind `main` as PRs merge. Add the open-source [`chinthakagodawita/autoupdate`](https://github.com/chinthakagodawita/autoupdate) GitHub Action to automatically keep open PR branches up to date with `main` as they progress. ## Scope - [ ] Add `.github/workflows/autoupdate.yml` triggered on `push` to `main`. - [ ] Use `chinthakagodawita/autoupdate`, pinned to a released version (prefer a commit SHA for supply-chain safety). - [ ] Auth via the default `GITHUB_TOKEN`; minimal `permissions` (`contents: write`, `pull-requests: write`); `PR_FILTER: all`. - [ ] Document the known trade-off that `GITHUB_TOKEN`-initiated updates do not re-trigger downstream workflow runs. ## Acceptance criteria - On a merge to `main`, other open PRs targeting `main` get their branches updated automatically. - Workflow YAML is valid. ## Notes Requested mid-flight by maintainer. Complements the CI ticket (#3); kept as a separate workflow file since it has a different trigger (`push: main`) and concern.
Sign in to join this conversation.