Disable repository-wide issue templates.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github
- Domain
- developer-experience
Research direction
Start by reviewing the organization-wide issue-template behavior described for vmware/.github and the repository-level GitHub settings that can override templates. Determine whether templates can be disabled for this organization; done means either removing the automatic templates or documenting the confirmed limitation and available opt-out path.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Github automatically applies issue templates from https://github.com/vmware/.github/ to all projects under the VMware org. This introduces a level or bureaucracy that is not suitable for all projects and that cannot be easily opted out of (to the best of my knowledge).
Describe the solution you'd like
Issue templates are useful in large projects with many external contributors in order to help streamline bug diagnostics and reduce the load on maintainers. However, such projects use highly customized templates designed to capture project-specific information. For a smaller project like ours, I prefer to make it as easy as possible for people to send their questions, requests, and bug reports by not imposing any structure. Speaking from personal experience, even a relatively simple form introduces an unnecessary barrier. And if the form has mandatory fields, I start to feel like it's the tax season :)
While github does allow us to override the set of templates per repo, I don't see a way to disable templates altogether once they are enabled for the org.
I would like to ask the maintainers of the vmware org to please reconsider the use of issue templates. Folks who want to use templates for their repos can add them with two clicks.
Describe alternatives you've considered
No response
Additional context
No response
- Dominant language
- Python
- Stars
- 1
- Forks
- 2
- Avg merge
- 16h 33m
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vmware/.github
-
failed secret-scanning
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
failed secret-scanning
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
failed secret-scanning
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
failed secret-scanning
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
mozilla/bedrock#17413 · 1 reaction ·
Maintainers usually reply within 2 days
-
instance instance add
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
searxng/searx-instances#943 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug tools
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
lance-format/lance#9655 ·
Maintainers usually reply within 2 days