Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Issue forms reference missing labels, so CLI/docs reports lose intended auto-labeling [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#21158•Fetched 2026-05-06 06:25:44
View on GitHub
Comments
2
Participants
2
Timeline
4
Reactions
0
Author
zichen0116zichen0116
Participants
mitre88mitre88zichen0116zichen0116
Timeline (top)
commented ×2labeled ×2

Code Example

existing labels include:
- documentation
- needs-response

missing labels referenced by templates:
- needs triage
- docs

---

labels:
  - bug
  - needs triage

---

labels: [docs]
RAW_BUFFERClick to expand / collapse

What issue are you seeing?

Two repository issue forms currently reference labels that do not exist in openai/codex, so new issues filed through those forms can miss the intended auto-labeling:

  • .github/ISSUE_TEMPLATE/3-cli.yml declares labels: [bug, needs triage], but the repo does not have a needs triage label.
  • .github/ISSUE_TEMPLATE/6-docs-issue.yml declares labels: [docs], but the repo does not have a docs label; the existing repo label is documentation.

This is a repo-owned workflow bug rather than a product behavior bug, but it directly affects issue triage quality and labeling consistency.

What steps can reproduce the bug?

  1. Inspect the issue form definitions in the repo:
    • .github/ISSUE_TEMPLATE/3-cli.yml
    • .github/ISSUE_TEMPLATE/6-docs-issue.yml
  2. Compare their declared labels with the current repo labels:
existing labels include:
- documentation
- needs-response

missing labels referenced by templates:
- needs triage
- docs

Repo-side evidence:

  • 3-cli.yml currently contains:
labels:
  - bug
  - needs triage
  • 6-docs-issue.yml currently contains:
labels: [docs]
  • gh label list -R openai/codex shows documentation and needs-response, but not docs or needs triage.

Additional impact surface:

  • the TUI feedback flow for external users builds GitHub issue links against template=3-cli.yml in codex-rs/tui/src/bottom_pane/feedback_view.rs, so that in-app path also routes through the affected CLI template metadata.

What is the expected behavior?

Issue forms should reference labels that actually exist in the repository, so issues opened from those forms receive the intended automatic labels.

Additional information

This looks like a narrow fix entirely within repo metadata:

  • align the issue template labels with the current repo labels, or
  • restore/create the missing labels if the template names are still the intended taxonomy.

I searched existing issues before filing and did not find one specifically tracking this issue-template label drift.

extent analysis

TL;DR

Update the issue template labels in .github/ISSUE_TEMPLATE/3-cli.yml and .github/ISSUE_TEMPLATE/6-docs-issue.yml to match the existing repository labels.

Guidance

  • Verify the current repository labels using gh label list -R openai/codex to ensure accuracy.
  • Update .github/ISSUE_TEMPLATE/3-cli.yml to replace needs triage with an existing label or create the needs triage label if intended.
  • Update .github/ISSUE_TEMPLATE/6-docs-issue.yml to replace docs with the existing documentation label.
  • Review the TUI feedback flow in codex-rs/tui/src/bottom_pane/feedback_view.rs to ensure it remains compatible with the updated template metadata.

Example

# Updated .github/ISSUE_TEMPLATE/3-cli.yml
labels:
  - bug
  - needs-response

# Updated .github/ISSUE_TEMPLATE/6-docs-issue.yml
labels: [documentation]

Notes

This fix assumes that the issue template labels are the only source of the problem. If the issue persists after updating the labels, further investigation may be necessary.

Recommendation

Apply the workaround by updating the issue template labels to match the existing repository labels, as this directly addresses the identified issue and ensures consistency in issue triage and labeling.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#runtime error#dependency conflict#environment setup#docker error#permission error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Issue forms reference missing labels, so CLI/docs reports lose intended auto-labeling [2 comments, 2 participants]