Repository navigation
[docs][harness] Delegate PR creation for dispatch-approved Issues to the PM - #662
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The user approved (2026-10-13) delegating PR creation to the PM for Issues whose dispatch the user approved, to cut the approval round trip that dominated Issue lead time (#655: ~12 h of a ~21 h lead time was waiting for PR approval).
AGENTS.md,CLAUDE.md: PR creation joins merge approval as a PM-delegated, condition-gated action.docs/dev/parallel-dev-harness.md: section 3, step 5 becomes "PR creation (PM)" with the conditions (verify gates on the pushed head, Linux cross-check withcargo-zigbuild clippy --all-targets --target x86_64-unknown-linux-gnu, files within 対象ファイル, security review 0 blockers or test/doc-only changes since the reviewed head, no open plan questions/high risk/unverified profile/harness paths). Changes the user must see first (user-visible defaults, weakened checks, schema migrations) still go to the user. Section 2 table, step 4a, step 6 and the auto-yes note follow.cfg(target_os = "macos")tests); the command reproduces those 7 errors locally in ~40 s.No code change. Merge approval conditions (step 6) are unchanged.
Verification
cargo test --test doc_drift: 23 passedpython3 -m pytest -q tests/test_codex_orchestrate.py: 73 passed🤖 Generated with Claude Code