Skip to content

🐛 Changelog-only base moves make green heads stale and trigger refreshes #19269

Closed

Description

@clubanderson

Problem

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).

Tests

  • changelog-only behind: current, no refresh
  • mixed base move: stale, refreshed
  • API error: stale
  • zero behind: unchanged

Activity

  1. self-assigned this
    on Nov 19, 2026
  2. clubanderson commented on Nov 19, 2026

    @clubanderson
    MemberAuthor

    Claiming this one; a PR is in progress.

  3. clubanderson commented on Nov 19, 2026

    @clubanderson
    MemberAuthor

    PR: #19270

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions