Skip to content

Enable Require merge queue on main-Branch ruleset #165

Description

@dborgards

Severity

High

Location

  • .github/workflows/ci.yml (approx. lines 8–18) — already triggers merge_group
  • Ruleset main-Branch (id 22609422)
  • GitHub reports mergeQueue: null

Problem

Issue #106 was closed as completed with a decision to enable the merge queue; the settings half was left to the maintainer. The ruleset requires OS + format checks and merge commits, but does not require the merge queue. Two green PRs can still land minutes apart and break main (see #85).

Proposed fix

  1. Enable Allow merge queues for the repo if needed.
  2. On ruleset main-Branch, enable Require merge queue.
  3. Set the queue merge method to merge commit (not squash — squash would change what semantic-release versions).

Decision question

None beyond confirming merge-commit (not squash) for the queue, as already preferred for this repo.

Review

From CanKit.Pro deep review of main @ 1cde1fc (2026-09-26).
Agent: https://cursor.com/agents/bc-39693a30-0a4f-5743-850f-1ab80aeb4dc5
Related: #106, #85

Activity

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

Metadata

Metadata

Assignees

Labels

area: buildBuild, packaging, release pipelineseverity/highHigh-severity finding from reviewtype: choreBuild, CI, tooling, housekeeping

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions