| ▲ | zzzeek 7 hours ago | ||||||||||||||||
Yes this is the identical pattern we strive for at SQLAlchemy. However github has no option to close issues to contributors only. These folks do what we do, they have an issue template called "do not use this". big whoop. People blow through those all day so we're clicking on "convert to discussion" all day. Github please add this feature! | |||||||||||||||||
| ▲ | efreak 6 minutes ago | parent | next [-] | ||||||||||||||||
Some of it may be unintentional. I've created issues directly through the `gh` CLI before, and issue templates don't show up there at all. If I haven't actually cloned the repo (or, more frequently, if I have a sparse checkout/deleted the files to save space), I have no way of knowing that there's a template and I'll just `gh issue -R some/thing create`. I finally moved on to the official GitHub app on mobile, but before that I used fasthub and other clients that had no idea about issue templates. GitHub really needs to add permissions to issues, so that users can't create issues without the template; any kind of failure in creation is a sign that you're doing something wrong. The ability to add tags to issues when creating via CLI would also be helpful. | |||||||||||||||||
| ▲ | jamietanna 6 hours ago | parent | prev [-] | ||||||||||||||||
We (Renovate) have an issue template (for maintainers/Triage-rights only) which has a label on it Then GitHub Actions runs on new Issues and any that have that label get auto-closed The idea is that folks with Triage+ can remove that label when creating an Issue, but not external contributors - might be worth giving that a go? | |||||||||||||||||
| |||||||||||||||||