Skip to content

chore: allow blank issues - #100

Merged
FeathBow merged 1 commit into
mainfrom
chore/allow-blank-issues
Sep 9, 2026
Merged

FeathBow merged 1 commit into
mainfrom
chore/allow-blank-issues

Conversation

@FeathBow

@FeathBow FeathBow commented Sep 9, 2026

Copy link
Copy Markdown
Owner

Summary

blank_issues_enabled was false, 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.md already 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:

cargo fmt --all -- --check
git diff --check

The file parses as YAML with blank_issues_enabled: true and the contact link intact. No Rust code is touched, so the workspace suite is unaffected; the pre-commit hook ran cargo fmt --check and cargo clippy --workspace --all-targets --locked -- -D warnings regardless, both clean.

Safety

  • Nothing about how a security report is filed changes. The contact link still routes those to the security policy, and both forms still carry the instruction not to use the public form for a report that could disclose a path or describe data loss outside the confirmed target set.
  • A blank issue carries none of the form's fields, so triage may have to ask for the version, environment, and reproduction that a form would have collected. That is the cost of the route existing, and it is smaller than a report never being filed.

@coderabbitai

coderabbitai Bot commented Sep 9, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: f7fb77a2-a1cb-421b-a51a-62016405e7b2


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.

@FeathBow
FeathBow merged commit 30b7b6b into main Sep 9, 2026
11 checks passed
@FeathBow
FeathBow deleted the chore/allow-blank-issues branch September 9, 2026 22:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant