andygrove opened a new pull request, #4768: URL: https://github.com/apache/datafusion-comet/pull/4768
## Which issue does this PR close? <!-- We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. For example `Closes #123` indicates that this PR will close issue #123. --> N/A. This is a small documentation and tooling change to the triage process. ## Rationale for this change The `requires-triage` label is auto-applied to every new issue, not just bug reports. The bug triage guide and the `bug-triage` skill, however, only described assigning priority and area labels, implicitly treating every triaged issue as a bug. As a result the `bug` label was applied inconsistently and was sometimes present on issues that are really feature requests. This makes the first triage decision explicit: classify each issue as a bug or an enhancement, and apply the matching type label. ## What changes are included in this PR? - `docs/source/contributor-guide/bug_triage.md`: add a "Type Labels" section describing the `bug` and `enhancement` labels and the rule that an issue must never carry both, that the type is decided from issue content rather than title wording, and that only bugs receive a priority label. The "For New Issues" steps now start with the bug-vs-enhancement decision. - `.claude/skills/bug-triage/SKILL.md`: the triage pass now classifies each issue as a bug or an enhancement first, applies `bug` (plus a priority) or `enhancement` (no priority), always removes the opposite type label so the two are mutually exclusive, and reports bugs and enhancements separately in the summary issue. ## How are these changes tested? Documentation and skill-instruction changes only; there is no code to test. The `gh` label commands in the skill use labels that already exist in the repository (`bug`, `enhancement`, the `priority:*` and `area:*` labels). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
