Consider allowing blank issues

Open Beginner friendly
#5 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
82/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github
Domain
tooling

Research direction

Start with .github/ISSUE_TEMPLATE/config.yml at the linked line and compare its setting with GitHub's issue-template chooser documentation. Enable blank issue creation, then verify that the repository's issue chooser offers a blank issue alongside the existing forms.

Written by the indexing model from the issue text.

Description

I'm trying to extract new issues from comments on https://github.com/hexpm/bob/issues/289.

While the move to standardize issues with the org level template and help guide contributions to the correct place is great for casual contributors, the original experience filing https://github.com/hexpm/bob/issues/289 was that I knew I'm in the right repo, but further having to select "Product or component" made me wonder where the issue would end up. Sorry that's a different issue.

I noticed I cannot bypass the forms and create a blank issue. I didn't find discussion about this specific point, so maybe it was not a deliberate decision.

https://github.com/hexpm/.github/blob/7a251663bc2f10976060b0cf0f577ef259e6957a/.github/ISSUE_TEMPLATE/config.yml#L1

@ericmj would you be open to enabling blank issues? This is how it looks like (first screenshot in the link): https://github.com/orgs/community/discussions/101943, and the docs https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser.

Dominant language
No language data
Stars
0
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hexpm/.github

All issues in hexpm/.github

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.