codex - 💡(How to fix) Fix CLI issue form has duplicate terminal description key [1 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#21270Fetched 2026-05-06 06:23:57
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
labeled ×2

Root Cause

Because external PRs are invitation-only per docs/contributing.md, I am not opening an unsolicited PR, but I have the two-line template cleanup prepared locally if maintainers want it.

Fix Action

Fix / Workaround

This is a small repo-metadata fix, not a runtime behavior change. A minimal patch would combine the two descriptions into one block scalar.

Code Example

- type: input
    id: terminal
    attributes:
      label: What terminal emulator and version are you using (if applicable)?
      description: Also note any multiplexer in use (screen / tmux / zellij)
      description: |
        E.g, VSCode, Terminal.app, iTerm2, Ghostty, Windows Terminal (WSL / PowerShell)
RAW_BUFFERClick to expand / collapse

What issue are you seeing?

The CLI issue form defines description twice for the same terminal-emulator input field:

  - type: input
    id: terminal
    attributes:
      label: What terminal emulator and version are you using (if applicable)?
      description: Also note any multiplexer in use (screen / tmux / zellij)
      description: |
        E.g, VSCode, Terminal.app, iTerm2, Ghostty, Windows Terminal (WSL / PowerShell)

In YAML, duplicate mapping keys are ambiguous and common parsers keep the latter value. In practice, the multiplexer guidance can be discarded by the second description key.

What steps can reproduce the bug?

  1. Inspect .github/ISSUE_TEMPLATE/3-cli.yml.
  2. Parse the issue templates with duplicate-key detection.

The duplicate is reported at lines 43 and 44 in the current template.

What is the expected behavior?

The terminal-emulator field should have one description key that preserves both pieces of guidance:

  • ask for any multiplexer in use;
  • provide examples such as VS Code, Terminal.app, iTerm2, Ghostty, and Windows Terminal.

Additional information

This is a small repo-metadata fix, not a runtime behavior change. A minimal patch would combine the two descriptions into one block scalar.

Because external PRs are invitation-only per docs/contributing.md, I am not opening an unsolicited PR, but I have the two-line template cleanup prepared locally if maintainers want it.

extent analysis

TL;DR

The issue can be fixed by combining the two description keys for the terminal-emulator input field into a single key with a multi-line value.

Guidance

  • Identify the duplicate description keys in the .github/ISSUE_TEMPLATE/3-cli.yml file and remove the second occurrence.
  • Combine the two descriptions into a single block scalar, preserving both pieces of guidance.
  • Verify the fix by parsing the issue templates with duplicate-key detection to ensure the error is resolved.
  • Review the updated template to confirm that the terminal-emulator field has a single description key with the expected guidance.

Example

  - type: input
    id: terminal
    attributes:
      label: What terminal emulator and version are you using (if applicable)?
      description: |
        Also note any multiplexer in use (screen / tmux / zellij).
        E.g, VSCode, Terminal.app, iTerm2, Ghostty, Windows Terminal (WSL / PowerShell)

Notes

This fix assumes that the YAML parser being used follows standard YAML parsing rules, where duplicate mapping keys are ambiguous and the latter value is kept.

Recommendation

Apply workaround: Combine the two description keys into a single key with a multi-line value, as this is a simple and effective fix for the issue.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING