Follow-up from the ai-flow plan (Cursor Plans ⇄ GitHub Issues Integration).
Context
ai-flow's /build command opens PRs whose bodies always carry a deterministic closing reference (Closes owner/repo#n). GitHub natively auto-closes the issue on merge, and the Projects v2 built-in workflow "item closed → Done" moves the board from there. What GitHub does not do natively is flip the linked issue to "In review" when the PR opens — Projects' built-in review workflows apply only to the PR item itself, not the linked issue.
Proposal
A small optional second reusable workflow in d3mlabs/ai-flow:
- Trigger:
pull_request: opened (and likely ready_for_review, closed)
- Resolve linked issues via GraphQL
closingIssuesReferences on the PR
- Set their Projects v2 status field via
updateProjectV2ItemFieldValue
Reliable precisely because ai-flow PR bodies always carry the closing reference.
Notes
- Created in
d3mlabs/dev because d3mlabs/ai-flow does not exist yet — transfer this issue there once the repo is created (rollout step of the plan).
Follow-up from the ai-flow plan (Cursor Plans ⇄ GitHub Issues Integration).
Context
ai-flow's
/buildcommand opens PRs whose bodies always carry a deterministic closing reference (Closes owner/repo#n). GitHub natively auto-closes the issue on merge, and the Projects v2 built-in workflow "item closed → Done" moves the board from there. What GitHub does not do natively is flip the linked issue to "In review" when the PR opens — Projects' built-in review workflows apply only to the PR item itself, not the linked issue.Proposal
A small optional second reusable workflow in
d3mlabs/ai-flow:pull_request: opened(and likelyready_for_review,closed)closingIssuesReferenceson the PRupdateProjectV2ItemFieldValueReliable precisely because ai-flow PR bodies always carry the closing reference.
Notes
d3mlabs/devbecaused3mlabs/ai-flowdoes not exist yet — transfer this issue there once the repo is created (rollout step of the plan).