chore: enable blank issues and add GitHub Community Support link in issue template#1337
Conversation
📝 WalkthroughWalkthroughThe GitHub issue template configuration was updated to enable blank issues and add a community support contact link, directing users to GitHub Discussions for general questions and community engagement. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
.github/ISSUE_TEMPLATE/config.yml (1)
3-5: Consider linking to the project’s own Discussions/support channel instead of GitHub global community.
https://github.com/orgs/community/discussionsmay redirect users away from HardwareVisualizer-specific help flow. If this repo has Discussions enabled, use that URL to keep support contextual.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/ISSUE_TEMPLATE/config.yml around lines 3 - 5, The template currently points the "name: GitHub Community Support" entry's url to the global community discussions URL; update the url field to the repository-specific Discussions/support URL (or remove/rename the entry to your repo's Discussions page) so users are routed to HardwareVisualizer's own support channel—modify the "name" and "url" YAML keys accordingly to reference the repo's Discussions link if Discussions is enabled.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In @.github/ISSUE_TEMPLATE/config.yml:
- Around line 3-5: The template currently points the "name: GitHub Community
Support" entry's url to the global community discussions URL; update the url
field to the repository-specific Discussions/support URL (or remove/rename the
entry to your repo's Discussions page) so users are routed to
HardwareVisualizer's own support channel—modify the "name" and "url" YAML keys
accordingly to reference the repo's Discussions link if Discussions is enabled.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yml
Review profile: CHILL
Plan: Pro
Run ID: 366cfd15-6ee0-4adb-bbe7-65ad5c8d4203
📒 Files selected for processing (1)
.github/ISSUE_TEMPLATE/config.yml
There was a problem hiding this comment.
Pull request overview
Enables opening blank issues on GitHub and adds a “GitHub Community Support” contact link to the issue template configuration to direct users to GitHub’s community discussions when needed.
Changes:
- Set
blank_issues_enabled: trueto allow blank issue creation. - Added a “GitHub Community Support” entry under
contact_links.
Summary
This pull request updates the issue template configuration to make it easier for users to submit blank issues and access community support. The most important changes are:
Improvements to issue submission and support:
blank_issues_enabledtotruein.github/ISSUE_TEMPLATE/config.yml, allowing users to submit issues without using a template.Related Issues
Type of Change
fix/branch)feat/branch)refactor/branch)docs/branch)chore/branch)Screenshots / Videos
Test Plan
Checklist
npm run lint && npm run format/cargo tauri-lint && cargo tauri-fmt)npm test/cargo tauri-test)