Skip to content

docs: no-duplicate PR rule for agents #116

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
DevVig wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

docs: no-duplicate PR rule for agents #116

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
9 changes: 9 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,3 +11,12 @@
- Claude reaches full control via FSEvents on `~/.claude/projects` journals; Cursor historically used hooks-only `ingest_lifecycle` (Limited)—ACP is the intended path toward Claude-parity.
- Community adapter “Setup needed” / “Waiting” usually means hooks or the host app are not yet delivering lifecycle events, not only a UI selection bug.
- Release pipeline is tag-driven: GitHub Release (DMGs/tarballs) → Homebrew formula bump PR → `finalize-release` smoke/promote; Intel finalize must use `brew services list --json` (not pipe-to-awk/grep) to avoid Broken pipe flakes.

## Before opening a pull request

1. **Search first.** Before creating a branch or PR for a named task, list open PRs in this repo (`gh pr list --state open` or GitHub search) and look for an existing PR whose title, branch, or description matches the same task (including drafts). Match on task intent, not only exact title — e.g. "independent PR review fallback", "Codex review fallback", same Linear/issue id.
2. **At most one open PR per task.** If an open PR already covers the task, do **not** open another. Update that PR's branch in place, or stop and report the existing PR URL. Renaming a branch (e.g. `codex/…` → `chore/…`) is **not** a reason to open a second PR: push the rename to the existing PR or close the old one in the same change and keep a single open PR.
3. **Fallback / review-policy PRs.** At most one open fallback, review-policy, or review-evidence setup PR per repo for the same design. If a newer approved design already merged (or is open) for that purpose, do not open a parallel draft of an older design — stop and report the superseding PR.
4. **Multi-repo rollouts.** When copying the same change across repos, check each target repo independently before opening. A shared payload hash or identical title across org repos is not permission to open a second PR in a repo that already has one.

If unsure whether two PRs are the same task, prefer updating the earlier open PR and ask the owner before opening another.
Loading