ci: label issues by area too (symmetric with PR labels) - #68
Merged
Conversation
PRs get frontend/backend/ci by path; issues only got platform:*. Add an "Area" dropdown to the bug form and generalise the labeler (renamed label-platform → label-issue) to map both Platform → platform:* and Area → frontend/backend/ci/ documentation. Also add a "Not platform-specific" Platform option so a build/CI/UI bug no longer has to pick a false OS.
8 tasks
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.
Summary
Follow-up to the PR auto-labeller (#67): give issues the same component labels PRs get. The bug form only set
platform:*; now it also sets a component label.label-platform.yml→label-issue.yml): map Platform →platform:*and Area →frontend/backend/ci/documentation, one label per group kept in sync on open/edit. Same label taxonomy as.github/labeler.ymluses for PRs.Affected layer
frontend/module/scripts/.github/Verification
actionlint .github/workflows/label-issue.ymlcleanfrontend/backend/build→ci/documentation); "Other" → no labelplatform:*### Area/### Platformfor the parser)Notes for reviewers
Both groups are single-select and authoritative from the form (the bot keeps exactly the chosen label per group, removing stale ones on edit). The
frontend/backend/cilabels were created on the repo in #67.