chore(ci): define Github labels as code with a workflow #93
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
qdm12
changed the title
ARR4N
requested changes
Dec 18, 2024
Easier than PR suggestions. I noticed that some useful labels were being deleted either entirely or to be replaced with effectively the same thing. --------- Signed-off-by: Arran Schlosberg <[email protected]> Co-authored-by: Quentin McGaw <[email protected]>
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.
Why this should be merged
Github issues are currently using the default github labels, and it would be good to have custom and easily customizable-as-code Github labels to better categorize Github issues.
How this works
labels.ymlusing crazy-max/ghaction-github-labeler to have Github labels as code in.github/labels.yml.github/labels.yml. Note:buglabel will be migrated toCategory: Bug 🐛labelDO NOT MERGElabel will be migrated toStatus: 🔴 DO NOT MERGElabels-skip.ymlto satisfy required workflow passing for pull requests (not set yet but should be set soon), triggering only on pull requests and when none of the labels related files are modified. This can be removed eventually as well, since we don't really need to make the labels workflow a required workflow, but I think it's a good-to-know at least during the PR review 😉 Also note it runs on every commit here since.github/workflows/labels-skip.ymlis not part of the ignored paths.How this was tested
Dry run on this pull request