This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

Both itd-115 and itd-2610110940216682 have abcd set up the merge queue when preparing a managed repository

issuewontfixminoriss-2610262042381184

Both itd-115 and itd-2610110940216682 have abcd set up the merge queue when preparing a managed repository

A scope leakage (severity minor) found by the cross-document consistency pass.

  • End A: .abcd/development/intents/drafts/itd-115-abcd-managed-repos-merge-prs-without-the.md:18 — "the forge tests it combined with the current base"
  • End B: .abcd/development/intents/drafts/itd-2610110940216682-a-person-whose-project-abcd-manages-gets.md:19 — "The full suite, on every operating system the project supports, runs once per change, in the merge queue, on exactly what will land"

itd-115 has onboarding configure a merge queue that tests each PR against the current base. itd-2610110940216682 has abcd, when it prepares the repository, set up the queue (sized to the runners) where the full suite runs once per change. The same ground is claimed twice with different contents, so it is unclear which draft owns the queue configuration.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1083.

Grounds

  • declined: Closed in the 2026-10-27 triage (dcn-2610271112330536) as a duplicate of iss-2610262042399506. The same draft, itd-2610110940216682, claims 'abcd sets this up' over ground another draft already owns; here the other draft is itd-115 and the ground is the merge queue, and one edit to itd-2610110940216682 (builds_on both, define the shape only) settles it.

Frontmatter

idiss-2610262042381184
typeissue
lifecyclewontfix
severityminor

References2

mentions2