OSS triage: add feature label to config, guidance, and 5-upvote escalation docs - #14560
Open
warp-agent-staging[bot] wants to merge 1 commit into
Open
OSS triage: add feature label to config, guidance, and 5-upvote escalation docs#14560warp-agent-staging[bot] wants to merge 1 commit into
warp-agent-staging[bot] wants to merge 1 commit into
Conversation
- Add the existing GitHub 'feature' label to .github/issue-triage/config.json so the OSS triage bot is permitted to apply it. - Specialize .agents/skills/triage-issue-local with guidance on when to apply feature vs bug/enhancement, and how feature and enhancement can relate. - Document in CONTRIBUTING.md that internal escalation for maintainer attention requires at least 5 upvotes, and that feature-labeled issues are not escalated through that path. Part of QUALITY-1366 (coordinated with warpdotdev/oz-for-oss and warpdotdev/ossie changes). Co-Authored-By: Oz <oz-agent@warp.dev>
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
Part of a coordinated three-repo change (
warpdotdev/oz-for-oss,warpdotdev/ossie,warpdotdev/warp) so OSS issue triage distinguishes feature requests from bugs, and internal escalation is gated on that distinction plus community demand.This repo's slice is docs + triage config only (no client code changes):
.github/issue-triage/config.json— added the existing GitHubfeaturelabel (This issue is a feature request, not a bug report.) to the taxonomy so the OSS triage bot is permitted to apply it..agents/skills/triage-issue-local/SKILL.md— added afeaturevsbug/enhancementguidance subsection under "Label taxonomy" (an overridable category per the coretriage-issueskill): applyfeaturefor genuinely new functionality, never for bug reports, and note whenenhancementandfeaturecan both apply.CONTRIBUTING.md— added an "Escalation for maintainer attention" note under Readiness labels documenting that internal escalation for triage attention requires at least 5 upvotes (👍 reactions), and thatfeature-labeled issues are never escalated through that path.Issue templates' seeded labels were left unchanged — the acceptance criteria didn't require touching them.
Verification
This is a testing-exempt change (config-only + pure documentation/guidance copy — a test could only assert the new label/text value, not detect a logic defect). No runtime behavior in this repo depends on these files:
.github/issue-triage/config.jsonis well-formed JSON (jq .).featurelabel already present onwarpdotdev/warp(colorf47f64, matching description)../script/presubmitcovers Rust source and is not applicable to this diff.Originating thread: https://warpdev.slack.com/archives/C0BDQDW8V5E/p1785447602533959