+1 for the first option, the bot may share link to #troubleshooting slack channel.
T. On Wed, Jul 8, 2020 at 4:24 PM Kaxil Naik <[email protected]> wrote: > I would go for (1) too. If it is a genuine problem they can tag a committer > who can open if need be. > > On Wed, Jul 8, 2020 at 3:22 PM Ash Berlin-Taylor <[email protected]> wrote: > > > I suspect 2 wouldn't result in fewer "help" questions, so I'd probably > > say 1 is the only way to go :( > > > > > > On Jul 8 2020, at 3:19 pm, Jarek Potiuk <[email protected]> > wrote: > > > > > Hello everyone. > > > > > > I noticed that despite being very explicit in the text of our > "Questions > > > and Support request" Github Issues template "**Do not use issues for > > > support requests or general help queries** > > > ", people are doing it and asking questions anyway - usually they do > not > > > read what is written there, simply delete/copy&paste their questions > over > > > it. I closed a number of such issues recently. > > > > > > I think we have two options: > > > > > > 1) Let the boring-cyborg bot close such issues immediately with > > appropriate > > > comment. > > > > > > 2) Remove "Question & Support Request" altogether from our templates. > > > > > > WDYT? > > > > > > J > > > > > > -- > > > > > > Jarek Potiuk > > > Polidea <https://www.polidea.com/> | Principal Software Engineer > > > > > > M: +48 660 796 129 <+48660796129> > > > [image: Polidea] <https://www.polidea.com/> > > > > > >
