In "choose a new issue type", selecting "Blank issue" goes back to the "choose an issue type" page

[pfmoore]

Description

As it says in the title - if you select "Blank issue (maintainers only)", you don't get a blank issue, you get the "pick an issue type" page again.

Expected behavior

You get a blank "new issue" page to fill in.

pip version

N/A

Python version

N/A

OS

N/A

How to Reproduce

1. Go to https://github.com/pypa/pip/issues/ and click the "New issue" button.
2. Select "(Maintainers only) Blank Issue".
3. A new tab opens, on the page https://github.com/pypa/pip/issues/new/choose

Presumably, this is because issues/new redirects to issues/new/choose if there's no template, but "Blank Issue" is intended to have no template...

Output

No response

Code of Conduct

• I agree to follow the PSF Code of Conduct.

[notatallshaw]

Can confirm, faced this today, it regressed at some point, presumably something on GitHub side changed

[ichard26]

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

	blank_issues_enabled: false
	contact_links:
	- name: "(maintainers only) Blank issue"
	url: https://github.com/pypa/pip/issues/new
	about: For maintainers only.

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]

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]

Could we simply have a template for "blank" issues that was, well..., blank?