Document blank issue access for maintainers when blank_issues_enabled is false#43456
Document blank issue access for maintainers when blank_issues_enabled is false#43456sunnyi101 wants to merge 1 commit intogithub:mainfrom
Conversation
… is false When blank_issues_enabled is set to false, users with write access or above (Write, Maintain, Admin) now still see the 'Blank issue' option in the template chooser with a 'Maintainers only' label. Contributors with Read or Triage access continue to only see configured templates. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
github-actions
bot
added
the
triage
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
There was a problem hiding this comment.
Pull request overview
Documents repository behavior where “Blank issue” remains available to maintainers (write access and above) even when blank_issues_enabled: false, clarifying what different permission levels see in the issue template chooser.
Changes:
- Added a note under “Configuring the template chooser” describing maintainer-only access to blank issues when blank issues are disabled.
| > [!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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
@copilot open a new pull request to apply changes based on this feedback
|
Closing this PR — the feature is still in staff ship and not yet GA. Moving to docs-internal instead. |
|
Moving to docs-internal per the Hubber contribution workflow. |
|
sunnyi101:blank-issues-maintainers-docs |
Summary
When
blank_issues_enabledis set tofalsein the issue template config, users with write access or above (Write, Maintain, or Admin roles) now still see the "Blank issue" option in the template chooser, labeled "Maintainers only." Contributors with Read or Triage access continue to only see the configured templates.This PR adds a note to the "Configuring the template chooser" section documenting this behavior.
Related
Changes
content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.mdto add a note explaining that maintainers (write access+) can still create blank issues even whenblank_issues_enabled: false.