averello/compound-engineering-plugin-mirror
1
0
Fork 0
mirror of https://github.com/EveryInc/compound-engineering-plugin.git synced 2026-06-19 15:41:46 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix: restore OPEN state check for existing PR detection

Browse Source 
gh pr view can return CLOSED/MERGED PRs on reused branches.
Without the state gate, the skill skips PR creation or edits
the wrong PR. Restores the check in both the full workflow
(Step 3) and the description-update flow (DU-2).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Trevin Chow
2026-03-27 00:38:16 -07:00
parent c68f8b4ab9
commit 7e11ae274e
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugins/compound-engineering/skills/git-commit-push-pr/SKILL.md
+4 -2
View File
@@ -41,7 +41,8 @@ gh pr view --json url,title,state
Interpret the result. Do not treat every non-zero exit as a fatal error here:
- If it returns PR data, an open PR exists for the current branch.
- If it returns PR data with `state: OPEN`, an open PR exists for the current branch.
- If it returns PR data with a non-OPEN state (CLOSED, MERGED), treat this as "no open PR." Report that no open PR exists for this branch and stop.
- If it exits non-zero and the output indicates that no pull request exists for the current branch, treat that as the normal "no PR for this branch" state. Report that no open PR exists for this branch and stop.
- If it errors for another reason (auth, network, repo config), report the error and stop.
@@ -133,7 +134,8 @@ gh pr view --json url,title,state
Interpret the result. Do not treat every non-zero exit as a fatal error here:
- If it **returns PR data**, an open PR exists for the current branch. Note the URL and continue to Step 4 (commit) and Step 5 (push). Then skip to Step 7 (existing PR flow) instead of creating a new PR.
- If it **returns PR data with `state: OPEN`**, an open PR exists for the current branch. Note the URL and continue to Step 4 (commit) and Step 5 (push). Then skip to Step 7 (existing PR flow) instead of creating a new PR.
- If it **returns PR data with a non-OPEN state** (CLOSED, MERGED), treat this the same as "no PR exists" -- the previous PR is done and a new one is needed. Continue to Step 4 through Step 8 as normal.
- If it **exits non-zero and the output indicates that no pull request exists for the current branch**, no PR exists. Continue to Step 4 through Step 8 as normal.
- If it **errors** (auth, network, repo config), report the error to the user and stop.