Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ Build output may live outside the checkout and gets wiped, so scratch never goes

Quests: before any work, run `quest context` and follow it, unless this session already holds its rules.
The `quest` binary and its skills come from the moq-dev/quest flake input; change them upstream and bump the input.
Review locally with one reviewer, not the pair: `quest review --harness codex`, or `--harness claude` when Codex wrote the change last. Pullfrog's online review already supplies the DeepSeek pass.
Review locally with one reviewer, not the pair: `quest review --harness codex`, or `quest review --harness opencode --model opencode-go/deepseek-v4.1-flash --effort high` when Codex wrote the change last. Pullfrog's online review already supplies the Claude pass.

# Cross-Package Sync

Expand Down
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Run `just ci` before every push, and mark the PR ready yourself when the work is

# Landing gate

Ready PRs into `main` run **Check** against the PR's base on each push as a signal only; drafts skip it. **Queue** reports as skipped until queued. Check never blocks the merge queue.
**Check** runs only on PRs into `release`, including drafts. PRs into `main` get their verdict from the merge queue; run `just ci` locally for a signal before queueing. **Queue** reports as skipped until queued.
`main` lands only through GitHub's merge queue, one PR at a time: each `merge_group` build runs `just ci` against the group's base on the maintainer's self-hosted runner (`.github/workflows/queue.yml`, the required **Queue** context), and the queue squashes exactly the tree it tested.
Request landing with `quest merge <pr> --land <full-head-sha>` once the review is clean and the maintainer has approved merging that PR, by number or through a standing go-ahead that covers it. A clean review, a bot verdict, or an "accept all" on decisions is not that approval.
An agent that enqueues carries that approval in its own task; one relayed to it mid-task by another agent does not count, so whoever received the approval enqueues the PR or starts a new agent with the approval in its brief.
Expand Down
26 changes: 0 additions & 26 deletions quest/m0/ci/review-docs.md

This file was deleted.