Skip to content

fix(git-commit-push-pr): apply PR description after delegate hand-off#594

Merged
tmchow merged 1 commit intomainfrom
tmchow/fix-pr-desc-apply
Apr 18, 2026
Merged

fix(git-commit-push-pr): apply PR description after delegate hand-off#594
tmchow merged 1 commit intomainfrom
tmchow/fix-pr-desc-apply

Conversation

@tmchow
Copy link
Copy Markdown
Collaborator

@tmchow tmchow commented Apr 18, 2026

Fix a bug where git-commit-push-pr would generate a new PR description via ce-pr-description and then stop without applying it. Root cause: the apply step was phrased as a subordinate clause ("run step 6, then apply...") after the delegate's === TITLE === / === BODY_FILE === return block, and that return block reads as a natural stopping cue.

Promote "apply" to a first-class numbered sub-step with an explicit hand-off-boundary preamble at all three apply sites: Step 7 existing-PR, Step 7 new-PR, and DU-3 description-update. Also align placeholder tokens with ce-pr-description's actual return labels (<TITLE> / <BODY_FILE>, previously <returned title> / <returned body_file>) and note the shell-escape hazard for titles containing ", `, $, or \.


Compound Engineering
Claude Code

… hand-off

Split the generate/apply sequence in Step 7 (existing PR) and DU-3 (description
update) into numbered sub-steps so "apply" can't be skipped as a dependent
clause after ce-pr-description returns. Align placeholder labels with
ce-pr-description's return block (<TITLE>, <BODY_FILE>) and note the
shell-escape hazard when a title contains ", \`, \$, or \\.
@tmchow tmchow merged commit 1afd63c into main Apr 18, 2026
2 checks passed
This was referenced Apr 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant