Repository navigation
Move the issue forms and design 0015 onto the org label standard - #284
Merged
Merged
Conversation
… standard jcrenshaw-dev now has one set of issue types and labels for every repository. The bug and enhancement labels became issue types and were deleted, so the forms set the type and needs-triage instead of labels that no longer exist.
|
No findings. The full review is encrypted in this run's |
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
1 participant
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.
This moves Baley onto the issue types and labels jcrenshaw-dev now uses in every repository, defined in the org label standard. The labels themselves were already changed through the API. The 18 issues labeled
bugare type Bug, the 54 labeledenhancementare type Enhancement, and the 15 labeleddesignare type Task and keep the label.bug,enhancementandquestionwere deleted once no issue depended on them, and the 39 open issues with no type haveneeds-triage.This pull request brings the repository in line with that. The bug form now sets the Bug type and
needs-triagein place of the deletedbuglabel, and the question form setsneeds-triagein place ofquestion. GitHub silently skips a form label that doesn't exist, so without this change new reports would arrive with neither. The Impact dropdown and every field are unchanged. In design 0015, UPK-R8, UPK-R9, the Labels section and their status rows now describe the org standard and the state read on 2026-10-18, in place of the label set from 2026-10-06.Both forms parse, and GitHub's preview of each on this branch shows the type and label with no template error. The counts in 0015 come from a GraphQL read of every issue on 2026-10-18. No code changes here, so the workspace suite was not run locally.