You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To pick up a draggable item, press the space bar.
While dragging, use the arrow keys to move the item.
Press space again to drop the item in its new position, or press escape to cancel.
While it would be easy to reenable blank issues, we trade one problem for another: the "create a blank issue" becomes a prominent option. For example, this is what it looks like the Black repository:
This could be too enticing and too visible such that users will file blank issues (ignoring our templates) because they aren't paying attention or thinking.
Although we don't actually get that many issues these days, so perhaps the risk of inadvertent blank issues is negligible? I'd be fine with flipping the configuration setting and seeing if there's any fallout. If there is, we can reassess.
Oh wait, we already have a giant button for creating new blank issues. The difference is that only people with write access to the project are (or rather, were) actually able to use it. Removing blank_issues_enabled: false would let anyone file blank issues.
This has been fixed by toggliing blank_issues_enabled to true in our issue template configuration. Ideally, it would be the very last option in the template list, but at least the bug and feature templates come first ¯\_(ツ)_/¯
Activity
notatallshaw commentedon Jun 5, 2025
Can confirm, faced this today, it regressed at some point, presumably something on GitHub side changed
ichard26 commentedon Jun 5, 2025
This is a recent change as GitHub rolls out the new issues experience: https://github.com/orgs/community/discussions/14287#discussioncomment-12622212
The TL;DR is that GitHub is enforcing
blank_issues_enabled: false
in the issue template configuration strictly.pip/.github/ISSUE_TEMPLATE/config.yml
Lines 4 to 8 in ab2a3f1
While it would be easy to reenable blank issues, we trade one problem for another: the "create a blank issue" becomes a prominent option. For example, this is what it looks like the Black repository:
This could be too enticing and too visible such that users will file blank issues (ignoring our templates) because they aren't paying attention or thinking.
Although we don't actually get that many issues these days, so perhaps the risk of inadvertent blank issues is negligible? I'd be fine with flipping the configuration setting and seeing if there's any fallout. If there is, we can reassess.
ichard26 commentedon Jun 5, 2025
Oh wait, we already have a giant button for creating new blank issues. The difference is that only people with write access to the project are (or rather, were) actually able to use it. Removing
blank_issues_enabled: false
would let anyone file blank issues.pfmoore commentedon Jun 5, 2025
Could we simply have a template for "blank" issues that was, well..., blank?
ichard26 commentedon Jul 8, 2025
This has been fixed by toggliing
blank_issues_enabled
totrue
in our issue template configuration. Ideally, it would be the very last option in the template list, but at least the bug and feature templates come first ¯\_(ツ)_/¯