feat: add release gate workflow (milestone closure check)#47
Closed
mpaulosky wants to merge 2 commits into
Closed
Conversation
- Add .github/workflows/release-gate.yml: blocks dev→main PRs when any active milestone has open issues (partially complete sprint detection) - Update release-myblog.md: document the automated gate, its logic, and add Project board check to Step 1 of the release checklist Gate logic: milestones with both open+closed issues are blocked; future milestones (only open) and completed milestones (only closed) are allowed. The workflow also posts a descriptive comment on blocked PRs. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
SummarySummary
CoverageAppHost - 0%
Domain - 93.4%
ServiceDefaults - 0%
Web - 68.1%
|
Contributor
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a
release-gate.ymlGitHub Actions workflow that enforces sprint milestone completion before anydev→mainPR can merge.Working as Boromir (DevOps/CI)
What this does
On every PR targeting
main, the gate checks all milestones for partially complete sprints — milestones with both open and closed issues. If found, it:Gate logic
To unblock: close or reassign the open issues to a future milestone.
Files changed
.github/workflows/release-gate.yml— new workflow.squad/playbooks/release-myblog.md— updated to document the gate and add Project board check to Step 1Why this matters
This enforces the principle: only fully-Done sprints ship to main. The Project #4 board's Done column is now the release readiness signal — no more manual "is everything done?" checks before releasing.
Closes no issue (infrastructure improvement).