don
/
neon-sprawl
mirror of https://github.com/ViPro-Technologies/neon-sprawl
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

chore: require Jira transition choice in story-end rule

pull/34/head
VinPropane 2026-04-08 23:15:58 -04:00
parent 491c75eca4
commit 8c23feb7cf
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.cursor/rules/story-end.md
View File

@ -27,9 +27,11 @@ If the user asks to **push** changes that sit on **`main`** and **`git push orig
- Do **not** delete **`main`** or **`origin/*`**. - Do **not** delete **`main`** or **`origin/*`**.
- Do **not** assume the remote story branch should be deleted unless the user asks (many teams keep `origin/NEON-…` for history or delete via GitHub UI). - Do **not** assume the remote story branch should be deleted unless the user asks (many teams keep `origin/NEON-…` for history or delete via GitHub UI).
## 4. Jira (optional) ## 4. Jira transition
- If the issue should move to **Done** (or equivalent), use Atlassian MCP when available; otherwise the user updates the board. This rule does **not** require Jira transitions. - Before finishing the story-end workflow, ask the user where the Jira story should move next: **`In Test`** or **`Done`**.
- After the user chooses one of those two states, perform the Jira transition with Atlassian MCP when available.
- If Atlassian MCP is unavailable or cannot complete the transition, tell the user and ask them to update the board manually.
## Related ## Related