zlacker

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!

>>zzzeek+(OP)
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?

>>jamiet+Qe
my fear is people are going to post issue reports, sometimes good ones that we need to act upon, they get autoclosed, and the submitter either never bothers to re-post or they are so annoyed that they don't re-post.

it would be way better if there was only one way for them to get their content in, in the first place

>>zzzeek+6L
In our case, we've fortunately not found that's happened - we do end up looking at Issues that are closed in this way, and the majority of cases it's someone who's raised a Discussion and want to bypass the triage so create a new Issue from their comment

(I'm thinking of getting some data and words together to look at how this has helped us over the last ~18 months)

>>zzzeek+(OP)
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.