Repository navigation
Implement the milestone enforcement workflow - #56
Draft
jeremystretch wants to merge 1 commit into
Draft
jeremystretch wants to merge 1 commit into
jeremystretch wants to merge 1 commit into
Conversation
jeremystretch
force-pushed
the
enforce-milestone-workflow
branch
from
October 27, 2026 18:45
abd5b2f to
abc7c7f
Compare
Member
Author
|
The CI failures appear to be unrelated to the PR. |
pheus
marked this pull request as draft
October 28, 2026 13:08
Collaborator
|
Thanks for adding this! I'm not assigning release milestones to issues yet, as we haven't had our first proper release. Once we enter beta, I'll start using them for release notes and planning. |
This branch has not been deployed
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.
Introduce a workflow that ensures any issues closed as completed get a release milestone assigned.