Conversation
Contributor
|
Documentation preview for this pull request is available at: |
4og
force-pushed
the
4og_aw_issue_triage
branch
from
September 3, 2026 10:01
a22b0b1 to
2f87b43
Compare
…and reopened issues
4og
force-pushed
the
4og_aw_issue_triage
branch
from
September 3, 2026 11:07
2f87b43 to
0219120
Compare
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 pull request introduces an automated workflow for triaging new and reopened issues, along with a configuration update to exclude certain files from linguist statistics. The most significant change is the addition of a detailed, maintainable issue triage process to streamline and standardize how issues are assessed and labeled.
Issue triage workflow:
.github/workflows/issue-triage.md, which defines a comprehensive, step-by-step process for assessing new and reopened issues, including instructions for gathering context, evaluating completeness, classifying and prioritizing issues, identifying duplicates, and posting a concise triage report for maintainers. The workflow restricts label and comment usage to maintain consistency and prevent over-labeling.Repository configuration:
.gitattributesto mark.github/workflows/*.lock.ymlfiles as linguist-generated, ensuring they are excluded from language statistics.…and reopened issues