Skip to content

chore(repo): remove dead top-level ISSUE_TEMPLATE/bug_report.yml - #1679

Closed
ColinM-sys wants to merge 1 commit into
NVIDIA:mainfrom
ColinM-sys:chore/remove-dead-issue-template
Closed

chore(repo): remove dead top-level ISSUE_TEMPLATE/bug_report.yml#1679
ColinM-sys wants to merge 1 commit into
NVIDIA:mainfrom
ColinM-sys:chore/remove-dead-issue-template

Conversation

@ColinM-sys

@ColinM-sys ColinM-sys commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Delete `ISSUE_TEMPLATE/bug_report.yml` (top level) and its now-empty parent directory.

Why

The file was added in #371 but landed in the wrong directory. GitHub only reads issue templates from `.github/ISSUE_TEMPLATE/` — not from a top-level `ISSUE_TEMPLATE/` folder — so this file has never had any effect on the issue creation flow. The four real, working templates (`bug_report.yml`, `config.yml`, `doc_issue.yml`, `feature_request.yml`) are correctly placed under `.github/ISSUE_TEMPLATE/` and continue to work.

The dead file also contains a copy-paste artifact:

```yaml
name: Bug Report
+description: Report a bug to help us improve NemoClaw
labels: ["status: triage"]
```

The leading `+` on line 2 is a stray diff fragment — so even if someone manually pointed at this path it would fail YAML schema validation. `grep -r "ISSUE_TEMPLATE/bug_report"` across the repo returns nothing, so no source file or workflow references the top-level path.

Test plan

  • `grep -r "ISSUE_TEMPLATE/bug_report"` (excluding `.github/`) → no references.
  • `.github/ISSUE_TEMPLATE/` is unchanged and still contains all four working templates.
  • No code, workflow, or doc references the deleted path.

Summary by CodeRabbit

  • Chores
    • Removed the GitHub issue template for bug reports.

The file at `ISSUE_TEMPLATE/bug_report.yml` (top level) was added in
PR NVIDIA#371 (\`Create bug_report.yml\`) but landed in the wrong directory.
GitHub only reads issue templates from \`.github/ISSUE_TEMPLATE/\`,
not from a top-level \`ISSUE_TEMPLATE/\` folder, so the file has
never had any effect on the issue creation flow. The four real
templates (\`bug_report.yml\`, \`config.yml\`, \`doc_issue.yml\`,
\`feature_request.yml\`) are correctly placed under
\`.github/ISSUE_TEMPLATE/\` and continue to work.

The dead file also contains a copy-paste artifact: line 2 starts with
a literal \`+description:\` (the leading plus is from a stray diff
fragment), so even if a user manually pointed to this file it would
fail YAML schema validation. No source file or workflow references
the top-level path (\`grep -r "ISSUE_TEMPLATE/bug_report"\` returns
nothing), so removing it is safe.

Removes the unused file and the now-empty parent directory.
@github-actions

github-actions Bot commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

This repository limits contributors to 10 open pull requests. Please close or merge existing PRs before opening new ones.

@github-actions github-actions Bot closed this Apr 9, 2026
@coderabbitai

coderabbitai Bot commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: f44f8241-34df-4f39-b30e-cb53b2c32bee

📥 Commits

Reviewing files that changed from the base of the PR and between e8b30a2 and 5405b39.

📒 Files selected for processing (1)
  • ISSUE_TEMPLATE/bug_report.yml

📝 Walkthrough

Walkthrough

The GitHub bug report issue template file was completely removed from the repository. This deletion eliminated the template configuration including metadata fields and form body sections that guided users through bug reporting.

Changes

Cohort / File(s) Summary
Issue Template Removal
ISSUE_TEMPLATE/bug_report.yml
Deleted entire bug report template configuration, including template name, description, labels, and form fields for "Steps to Reproduce" and "Error Logs / Traceback".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A template once stood, neat and gray,
For bugs and their tales, now swept away,
No "steps to reproduce" shall we see,
The traceback logs wild and free!
Simpler it is, carefree we hop,
Into the void, we let it drop! 🌙

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@wscurran wscurran added the chore Build, CI, dependency, or tooling maintenance label Jun 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore Build, CI, dependency, or tooling maintenance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants