Skip to content

chore(#488): ship status-in-dev automation to main - #492

Merged
vybe merged 1 commit into
mainfrom
release/in-dev-automation
Apr 24, 2026
Merged

chore(#488): ship status-in-dev automation to main#492
vybe merged 1 commit into
mainfrom
release/in-dev-automation

Conversation

@vybe

@vybe vybe commented Apr 24, 2026

Copy link
Copy Markdown
Contributor

Ships the status-in-dev label + PR-merge workflow to main ahead of the next full release, so issue-state tracking is live everywhere immediately.

Narrow cherry-pick of ef6cfdb (from #489) — does not include the WEBHOOK-001 feature still staged on dev.

Closes #488

Contents

  • .github/workflows/issue-status-on-merge.yml — on PR-merge-to-dev, parse Fixes/Closes/Resolves #N → add status-in-dev, remove status-in-progress
  • .claude/skills/release/SKILL.md/release uses status-in-dev as authoritative shipping list; emits Closes #N in release PR
  • docs/DEVELOPMENT_WORKFLOW.md — SDLC updated to Todo → In Progress → In Dev → Done

Test plan

🤖 Generated with Claude Code

Close the gap between "PR merged to dev" and "released to main".

- New GH Action `issue-status-on-merge.yml`: on PR merge to dev,
  parse Fixes/Closes/Resolves #N from PR body+title, add
  `status-in-dev`, remove `status-in-progress`.
- `/release` skill: read `gh issue list --label status-in-dev` as
  the authoritative shipping list for release notes; include
  `Closes #N` in the release PR body so issues auto-close on merge
  to main.
- `DEVELOPMENT_WORKFLOW.md`: SDLC is now Todo → In Progress →
  In Dev → Done, each stage mapped 1:1 to commit-graph location.

Fixes #488

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vybe
vybe merged commit 167c375 into main Apr 24, 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.

Wire up status-in-dev label and PR-merge automation

1 participant