The auto-update workflow only fired on push to main, so a PR opened during a quiet period (no subsequent merge to main) sat behind main until it was manually updated — e.g. #256.
Add a pull_request trigger (opened, reopened, ready_for_review) alongside the existing push trigger so newly-opened PRs get auto-updated immediately. synchronize is intentionally excluded — it fires on every commit push, including the autoupdate action's own branch-update pushes, which would cause wasteful re-runs / near-loops.
## Summary
- The auto-update workflow only fired on `push` to `main`, so a PR opened during a quiet period (no subsequent merge to `main`) sat behind `main` until it was manually updated — e.g. #256.
- Add a `pull_request` trigger (`opened`, `reopened`, `ready_for_review`) alongside the existing `push` trigger so newly-opened PRs get auto-updated immediately. `synchronize` is intentionally excluded — it fires on every commit push, including the autoupdate action's own branch-update pushes, which would cause wasteful re-runs / near-loops.
Closes #259
🤖 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
pushtomain, so a PR opened during a quiet period (no subsequent merge tomain) sat behindmainuntil it was manually updated — e.g. #256.pull_requesttrigger (opened,reopened,ready_for_review) alongside the existingpushtrigger so newly-opened PRs get auto-updated immediately.synchronizeis intentionally excluded — it fires on every commit push, including the autoupdate action's own branch-update pushes, which would cause wasteful re-runs / near-loops.Closes #259
🤖 Generated with Claude Code