Skip to content

docs(ci, AGENTS.md): the merge queue runs the affected set, not the full package list — two stale sentences corrected #16573

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
claude wants to merge 1 commit into
base: main
Choose a base branch
from
+5 −5
Draft

docs(ci, AGENTS.md): the merge queue runs the affected set, not the full package list — two stale sentences corrected #16573

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -499,8 +499,8 @@ Even inside your own worktree, operate defensively:

**Re-arm awareness** — none of these is a reason to avoid the queue; all are reasons to
confirm a PR is still *in* it: a red queue build **ejects** your entry and drops
auto-merge, often on a package your PR never touched (the queue runs the full suite; the
PR ran affected-only) — diagnose against `merge-queue-triage.yml`'s comment, recognise a
auto-merge, often on a package your PR never touched (it runs the merge group's affected
set, not just yours) — diagnose against `merge-queue-triage.yml`'s comment, recognise a
known-flaky signature, then re-arm once, never reflexively; **collateral eviction is
silent** (triage comments only on `failure`, so an entry cancelled because something
*ahead* failed gets nothing) — neither on `main` nor in the queue means dropped, re-arm;
Expand Down
6 changes: 3 additions & 3 deletions scripts/check-cross-package-test-inputs.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,9 @@
//
// Layer B -- turbo's task cache. `test` declares `inputs: ["$TURBO_DEFAULT$",
// ...]`, which is PACKAGE-LOCAL. `@objectstack/spec#test` therefore hashes
// the same before and after any change outside `packages/spec`, so even the
// merge-queue and push builds -- which deliberately partition the FULL
// package list, not the affected subset -- replay a cached green.
// the same before and after any change outside `packages/spec`, so even a
// build that partitions the FULL package list -- `push` on `main` today,
// the merge queue too until #16453 -- replays a cached green.
// Measured: `turbo run test --filter=@objectstack/spec` after the
// platform-objects edit printed `>>> FULL TURBO`, 42ms, replaying the
// previous run's log, while `--force` on the same tree failed the scan.
Expand Down
Loading