chore: allow blank issues - #100
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 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. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
blank_issues_enabledwasfalse, so the template chooser offered only the bug and feature forms. That is the right default when every report fits one of them, but it also means a reporter with something that fits neither — a question, a packaging problem, a documentation error — has no route at all, while a maintainer can still file one from the issues page. The barrier fell on exactly the people least able to work around it.Enabling blank issues restores that route. The two forms remain, stay first in the chooser, and keep carrying the fields that make a report triageable; the blank option is the escape hatch beneath them.
Preserved behavior. Both forms, their labels, their title prefixes, and the security contact link are unchanged.
CONTRIBUTING.mdalready points at/issues/new/choose, which is the chooser this affects, so the link stays correct and simply gains an option. The security policy remains the route for anything sensitive, and it is still the only contact link.Validation
Passed locally on this branch:
The file parses as YAML with
blank_issues_enabled: trueand the contact link intact. No Rust code is touched, so the workspace suite is unaffected; the pre-commit hook rancargo fmt --checkandcargo clippy --workspace --all-targets --locked -- -D warningsregardless, both clean.Safety