You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
🐛 Changelog-only base moves make green heads stale and trigger refreshes #19269
On repositories gated by auto_merge.require_current_base, any base move makes a green head stale and sends it to base preparation, which refreshes the branch and re-runs every workflow on the new head.
Over the last 48 hours on v5 there were 258 merges and 133 bot base refreshes. 58 of the 258 base moves (22%) were CHANGELOG-only release-gate merges. Each refresh costs about 16 workflow runs and about 38 runner-minutes, yet a base move that only touches CHANGELOG.md or changelog.d/ cannot change anything CI tests.
Proposed fix
In currentBaseGate (src/pkg/github/automerge/automerge_current_base.go), when the head is behind, compare the PR's merge base with the base tip. If every changed file is the root CHANGELOG.md or under the root changelog.d/ (a named, documented allowlist constant) and the PR itself changes none of those files, report the head as current with the reason behind only by changelog-only commits instead of sending it to preparation.
Fail closed: a missing merge base, any API error, a possibly truncated compare, or any other path keeps today's behavior (stale, refreshed).
Activity
clubanderson commentedon Nov 19, 2026
Claiming this one; a PR is in progress.
clubanderson commentedon Nov 19, 2026
PR: #19270