[RFC] [WIP] Wishlist of behaviours for the bot

[Lorenzo Sciandra]

I'm using this issue to list all the different behaviours I wish this bot would have.

Overall idea

Basically, the purpose of this bot would be to help out in keeping the issues & PRs sections of react-navigation "clean".

My definition of clean basically means that every open issue is:

• a bug that needs a code fix
• a modification the documentation needs
• a feature that multiple people (+1 at least one "good rep dev") think it's useful

List of behaviours

• Reply to (new) question tagged issues

When a new issue gets tagged with as question, the bot should close it and reply with:

Hi @(user)! It looks like this is not a bug of the library nor a feature request, so I'll close it: I suggest next time you use [Stack Overflow](https://stackoverflow.com/search?q=react-navigation) which is better suited for answering these types of questions. I also encourage you to join the [Reactiflux](https://www.reactiflux.com/) community on Discord. There are React Native and React Navigation channels with helpful people who might be able to answer your question. I would also like to mention that there is a collection of helpful links and tutorials for React Navigation in the [README](https://github.com/react-community/react-navigation#community-contributions) which might be helpful for you.

If you believe that you are experiencing a bug or have a feature request, please open a new Issue following the dedicated template or submit a PR.

Currently after the first paragraph I add a second with some extra info to point the user in the right direction (ex. if the question is about the Drawer I link them to the README section with the Drawer article series by Gant ) but the bot surely won't be able to. #goodenough

• Autoclose issues that don't follow any template

When a user create an issue that doesn't follow the template, it should close it right away saying something along these lines:

Closing because you haven't followed the issue template; please open a new one that follows the template.
Without that, it's nearly impossible to understand & investigate the issue. I suggest you also try (in the new issue) to answer/explain in a way that fits these questions:

1. have you tried updating to the latest release?
1. does it happen only on Android/iOS?
1. does it happen on both Debug and Release modes?
1. does it happen with Debugger On or Off? Both?
1. Can you provide a GIF or a repo or a snack to reproduce this issue?

Maybe we should add an invalid tag that triggers this behaviour too?

Other notes

• I want to play with the issue templates, since I joined the OSM I've already learned that we could create multiple templates. I'll write some more later on.

---

This is not the full list of behaviours yet, but I decided to start writing it anyway to not forget/delay this further.