Repository navigation
Add Website auto-labeling for frontend PRs - #69
Merged
Merged
Conversation
Co-authored-by: 0x5t4l1n <161853795+0x5t4l1n@users.noreply.github.com>
0x5t4l1n
marked this pull request as ready for review
October 28, 2026 17:09
0x5t4l1n
approved these changes
Oct 28, 2026
Contributor
✅ No duplicate payload entries detectedChecked 0 normalized entries from added/modified payload files on the latest push. Posted automatically by the Duplicate Payload Check workflow. |
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.
Recent PRs that modified website code were not receiving a suitable label, making triage inconsistent with existing repository labeling patterns. This updates the labeler rules so website-scope changes are tagged automatically.
What changed
Websiterule in.github/labeler.yml.src/**public/**Why this addresses the issue
Rule added