docs: require milestones when creating issues - #171
Merged
Merged
Conversation
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
2 participants
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.
Require every issue to have a milestone in its creation request, including bugs, chores, releases, and follow-ups. Select or create the milestone first, then verify the assignment. Assigning it after creation is explicitly prohibited.
Closes #170
Validation: git diff --check and npm run validate passed, including version metadata, lint, TypeScript, 593 tests and all 21 Expo Doctor checks. Independent review of 60c83d8 found no actionable findings. All hosted CI passed: validation and Android/iOS native builds. CI run: https://github.com/switchifyapp/switchify-remote/actions/runs/34779567204