Skip to content

Document blank issue access for maintainers when blank_issues_enabled is false #43456

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sunnyi101 wants to merge 1 commit into from
+3 −0
Closed

Document blank issue access for maintainers when blank_issues_enabled is false #43456

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions ...ful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,9 @@ Here is the rendered version of the issue form.

You can encourage contributors to use issue templates by setting `blank_issues_enabled` to `false`. If you set `blank_issues_enabled` to `true`, people will have the option to open a blank issue.

> [!NOTE]
> When `blank_issues_enabled` is set to `false`, users with write access or above (Write, Maintain, or Admin roles) will still see the "Blank issue" option in the template chooser, labeled "Maintainers only." This allows maintainers to bypass template restrictions when needed. Contributors with Read or Triage access will only see the configured templates.
> [!NOTE]
> If you used the legacy workflow to manually create an `issue_template.md` file in the `.github` folder and enable blank issues in your _config.yml_ file, the template in `issue_template.md` will be used when people choose to open a blank issue. If you disable blank issues, the template will never be used.
Comment on lines +68 to 72
Copy link

Copilot AI Mar 19, 2026

Choose a reason for hiding this comment

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

This section now has two consecutive [!NOTE] alerts (lines 68–72). Our docs style guidance discourages consecutive alerts / multiple alerts in the same section; it makes the page harder to scan. Consider merging the new maintainer behavior into the existing NOTE, or converting one of these NOTES into regular body text so there’s only a single alert here.

Copilot uses AI. Check for mistakes.
Copy link
Author

@sunnyi101 sunnyi101 Mar 19, 2026

Choose a reason for hiding this comment

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

@copilot open a new pull request to apply changes based on this feedback

Expand Down
Loading