feat: order issue templates numerically and fix contact links config#891
Conversation
Renames issue template files with numerical prefixes (01-bug-report.yml, 02-feature-request.yml, 03-epic.yml) to guarantee explicit ordering in the GitHub UI chooser menu without altering their clean display names. Also removes the redundant security policy contact link (which GitHub auto-creates) and fixes YAML comment rendering for the Slack contact link description.
✅ Deploy Preview for agent-sandbox canceled.
|
There was a problem hiding this comment.
Pull request overview
This PR refines the repository’s GitHub issue intake configuration to improve the ordering and rendering of issue templates in the GitHub “New issue” chooser, and to ensure contact links render correctly.
Changes:
- Renames/introduces issue form templates with numeric prefixes (
01-,02-,03-) to enforce deterministic ordering in the GitHub UI. - Simplifies
.github/ISSUE_TEMPLATE/config.ymlby removing the explicit vulnerability contact link (relying on GitHub’s security-policy injection) and quotingaboutstrings so#agent-sandboxisn’t parsed as a YAML comment. - Adds an “Epic / Umbrella Issue” form intended for maintainers to track larger initiatives.
Reviewed changes
Copilot reviewed 1 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.github/ISSUE_TEMPLATE/config.yml |
Removes redundant vulnerability contact link and quotes about fields to avoid YAML # comment parsing. |
.github/ISSUE_TEMPLATE/01-bug-report.yml |
Adds bug report issue form with security policy guidance and structured fields. |
.github/ISSUE_TEMPLATE/02-feature-request.yml |
Adds feature request issue form with structured prompt fields. |
.github/ISSUE_TEMPLATE/03-epic.yml |
Adds maintainer-focused epic issue form with task breakdown and milestone fields. |
|
/lgtm |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aditya-shantanu, barney-s, janetkuo The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Looks like a test flake of TestSandboxClaimTTLZeroRetainPreservesFinishedConditionDuringCleanup |
…ubernetes-sigs#891) Renames issue template files with numerical prefixes (01-bug-report.yml, 02-feature-request.yml, 03-epic.yml) to guarantee explicit ordering in the GitHub UI chooser menu without altering their clean display names. Also removes the redundant security policy contact link (which GitHub auto-creates) and fixes YAML comment rendering for the Slack contact link description.
…ubernetes-sigs#891) Renames issue template files with numerical prefixes (01-bug-report.yml, 02-feature-request.yml, 03-epic.yml) to guarantee explicit ordering in the GitHub UI chooser menu without altering their clean display names. Also removes the redundant security policy contact link (which GitHub auto-creates) and fixes YAML comment rendering for the Slack contact link description.
What this PR does / why we need it:
Refines the newly added issue templates for
agent-sandboxto guarantee explicit ordering in the GitHub UI chooser menu and correct contact link rendering.Specifically, this PR:
01-bug-report.yml,02-feature-request.yml,03-epic.yml) so GitHub sorts them in the exact desired order in the chooser UI, without altering their clean display names.config.yml, as GitHub automatically injects one when a security policy is present.aboutdescription in quotes to prevent the#agent-sandboxchannel name from being treated as a YAML comment.Which issue(s) this PR is related to:
NONE
Release Note