Skip to content

ci: two independently green PRs turned main red; add a merge queue #661

Description

@kyle-sexton

Problem

#650 (removed docs/topics/) and #656 (added AGENTS.md links into docs/topics/) were each green against their own base and merged in parallel. Main went red on lychee-offline and selector-contract at c11c7ec, and every open PR inherited the failure until #660 repaired it. #659 was blocked behind it.

main's ruleset requires ci-status with strict_required_status_checks_policy: false and has no merge_queue rule (read from gh api repos/melodic-software/ci-workflows/rules/branches/main on 2026-10-03). claude-code-plugins' main has a merge queue (ALLGREEN, squash), which tests each PR against the queue head.

Proposal

Add a merge-queue rule to ci-workflows main (through github-iac), matching claude-code-plugins, so a PR is re-tested on top of whatever merged before it. The cheaper alternative, strict required checks, forces a branch update per merge and suits a low-volume repo less well.

Evidence

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageNot yet classified. Floor until a type and one priority tier are set.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions