autoupdate.yml previously only rebased PRs with GitHub auto-merge armed (PR_FILTER: "auto_merge"), leaving other open PRs to fall behind main and requiring manual branch updates.
Switch PR_FILTER to "all" so every open PR is kept up to date as main advances, not just auto-merge-armed ones.
Update the header comment to describe the new "all open PRs" behavior instead of the old auto-merge-only behavior, while keeping the existing note that this requires the AUTOUPDATE_TOKEN PAT (not the default GITHUB_TOKEN) so the branch update re-triggers the PR's CI.
Also renamed the job/step names (Auto-update open PRs / Update all behind PRs) since the old names described the auto-merge-only behavior.
No other workflow settings changed: on: trigger, permissions, concurrency, environment: CI_CD, and the pinned action SHA are untouched.
Test plan
python -c "import yaml; yaml.safe_load(open('.github/workflows/autoupdate.yml')); print('yaml ok')" → yaml ok
Reviewed diff to confirm only PR_FILTER and the header comment (plus job/step display names) changed; GITHUB_TOKEN, MERGE_CONFLICT_ACTION, on:, permissions, concurrency, environment, and the pinned action SHA are unchanged.
Workflow-file-only change with no app code, so no Gradle build/tests are needed.
## Summary
- `autoupdate.yml` previously only rebased PRs with GitHub auto-merge armed (`PR_FILTER: "auto_merge"`), leaving other open PRs to fall behind `main` and requiring manual branch updates.
- Switch `PR_FILTER` to `"all"` so every open PR is kept up to date as `main` advances, not just auto-merge-armed ones.
- Update the header comment to describe the new "all open PRs" behavior instead of the old auto-merge-only behavior, while keeping the existing note that this requires the `AUTOUPDATE_TOKEN` PAT (not the default `GITHUB_TOKEN`) so the branch update re-triggers the PR's CI.
- Also renamed the job/step names (`Auto-update open PRs` / `Update all behind PRs`) since the old names described the auto-merge-only behavior.
- No other workflow settings changed: `on:` trigger, `permissions`, `concurrency`, `environment: CI_CD`, and the pinned action SHA are untouched.
## Test plan
- [x] `python -c "import yaml; yaml.safe_load(open('.github/workflows/autoupdate.yml')); print('yaml ok')"` → `yaml ok`
- [x] Reviewed diff to confirm only `PR_FILTER` and the header comment (plus job/step display names) changed; `GITHUB_TOKEN`, `MERGE_CONFLICT_ACTION`, `on:`, `permissions`, `concurrency`, `environment`, and the pinned action SHA are unchanged.
- Workflow-file-only change with no app code, so no Gradle build/tests are needed.
Closes #243
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
autoupdate.ymlpreviously only rebased PRs with GitHub auto-merge armed (PR_FILTER: "auto_merge"), leaving other open PRs to fall behindmainand requiring manual branch updates.PR_FILTERto"all"so every open PR is kept up to date asmainadvances, not just auto-merge-armed ones.AUTOUPDATE_TOKENPAT (not the defaultGITHUB_TOKEN) so the branch update re-triggers the PR's CI.Auto-update open PRs/Update all behind PRs) since the old names described the auto-merge-only behavior.on:trigger,permissions,concurrency,environment: CI_CD, and the pinned action SHA are untouched.Test plan
python -c "import yaml; yaml.safe_load(open('.github/workflows/autoupdate.yml')); print('yaml ok')"→yaml okPR_FILTERand the header comment (plus job/step display names) changed;GITHUB_TOKEN,MERGE_CONFLICT_ACTION,on:,permissions,concurrency,environment, and the pinned action SHA are unchanged.Closes #243
🤖 Generated with Claude Code