Skip to content

chore(github): update bug report template with build selection#529

Merged
zachyale merged 1 commit into
grimmory-tools:developfrom
obviouslyallie:chore/bug_request_template
Apr 16, 2026
Merged

chore(github): update bug report template with build selection#529
zachyale merged 1 commit into
grimmory-tools:developfrom
obviouslyallie:chore/bug_request_template

Conversation

@obviouslyallie

@obviouslyallie obviouslyallie commented Apr 15, 2026

Copy link
Copy Markdown
Contributor

Description

Added a build version option in the bug template for GitHub
Options between Stable, Nightly, and Release Candidate
https://i.imgur.com/C8UGufM.png

Linked Issue: Fixes #471

Changes

Adds a dropdown to issue template with options for build version. It must be selected but defaults to Stable.

Summary by CodeRabbit

  • Chores
    • Added a required build version field to the bug report template, allowing users to specify whether they are using Stable, Nightly, or Release Candidate builds when submitting issues.

@coderabbitai

coderabbitai Bot commented Apr 15, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

A new required dropdown field was added to the bug report issue template to capture the Grimmory build version (Stable, Nightly, Release Candidate) with a default value and additional whitespace at the end.

Changes

Cohort / File(s) Summary
Bug Report Template
.github/ISSUE_TEMPLATE/bug_report.yml
Added required dropdown field (build) for specifying build version with options (Stable, Nightly, Release Candidate) and default selection; appended blank lines to template.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

chore

Poem

🐰 A dropdown appears, so shiny and new,
To catch which Grimmory build users pursue,
Stable or Nightly, the choice is now clear,
Bug reports shall flourish throughout the whole year! ✨

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Linked Issues check ⚠️ Warning The PR adds build selection dropdown to bug report template as required [#471], but auto-labeling functionality for Nightly selection is not implemented. Implement automation to apply 'Nightly' label to issues when Nightly build is selected, or update issue #471 if this is deferred to a follow-up PR.
Out of Scope Changes check ⚠️ Warning The PR adds extra blank lines at the end of the template file, which is not mentioned in issue #471 requirements and appears to be an unrelated change. Remove the extra blank lines at the end of the template file to keep changes focused on the build selection dropdown feature.
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title follows conventional commit format with 'chore(github):' prefix and clearly describes the change of updating the bug report template.
Description check ✅ Passed The description includes all required sections (Description, Linked Issue) and provides clear details about the changes, though missing explicit Changes section heading.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

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

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@coderabbitai coderabbitai Bot added the chore label Apr 15, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/ISSUE_TEMPLATE/bug_report.yml:
- Around line 72-84: The issue is that the new dropdown field with id "build"
does not automatically apply a "Nightly" label when users select Nightly; add a
GitHub Actions workflow (e.g., a new file under .github/workflows) triggered on
issues.opened and issues.edited that reads the "build" field from the incoming
issue body/issue_form payload and, when value equals "Nightly", uses a
label-adding action or the GitHub REST API to add the pre-created "Nightly"
label to the issue; ensure the workflow references the "build" field name and
guards against missing labels by either creating the label beforehand or
checking existence before applying.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8b6e4128-9be7-4620-9f9b-b7847391ebf8

📥 Commits

Reviewing files that changed from the base of the PR and between 41ccd64 and 86a77b6.

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

Comment thread .github/ISSUE_TEMPLATE/bug_report.yml

@balazs-szucs balazs-szucs left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you :)

@zachyale zachyale merged commit 8e68327 into grimmory-tools:develop Apr 16, 2026
14 checks passed
@obviouslyallie obviouslyallie deleted the chore/bug_request_template branch April 19, 2026 20:04
dsmouse pushed a commit to dsmouse/grimmory that referenced this pull request May 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Indicate Nightly Version on Bug Report

3 participants