Add guidelines for managing GitHub issues

Reviewed By: mkonicek

Differential Revision:D2971827
Ninja: oss only

fb-gh-sync-id: b86b74a8a582f159777fb90da23645ee730a4802
shipit-source-id: b86b74a8a582f159777fb90da23645ee730a4802

ISSUE_TEMPLATE.md

@@ -11,7 +11,7 @@ Can you see anything in the logs? Can you debug why this happens? **Send a pull
 
 Have a question or not sure you've found a bug?
 -----------------------------------------------------------------
-Please ask your question [StackOverflow](http://stackoverflow.com/questions/tagged/react-native) with the tag `react-native`. StackOverflow is amazing for Q&A. Because of the reputation system it is likely the community will see and answer your question there.
+Please ask your question on [StackOverflow](http://stackoverflow.com/questions/tagged/react-native) with the tag `react-native`. StackOverflow is amazing for Q&A. Because of the reputation system it is likely the community will see and answer your question there.
 
 Make sure you **include a short code snippet to demonstrate the problem**.
 

bots/IssueCommands.txt

@@ -1,5 +1,5 @@
 /answered
-comment Closing this issue as {author} says the question asked has been answered. Please help us by asking questions on [StackOverflow](http://stackoverflow.com/questions/tagged/react-native). StackOverflow is amazing for Q&A. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only.
+comment Closing this issue as {author} says the question asked has been answered. Please help us by asking questions on [StackOverflow](http://stackoverflow.com/questions/tagged/react-native). StackOverflow is amazing for Q&A: it has a reputation system, voting, the ability to mark a question as answered. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only.
 close
 
 /duplicate (#[0-9]+)
@@ -11,12 +11,17 @@ comment The /expected comment above tells me this is expected behavior. Closing
 close
 
 /question
-comment Hey {issue_author} and thanks for posting this! {author} tells me this issue looks like a question that would be best asked on [StackOverflow](http://stackoverflow.com/questions/tagged/react-native). StackOverflow is amazing for Q&A. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only.
+comment Hey {issue_author} and thanks for posting this! {author} tells me this issue looks like a question that would be best asked on [StackOverflow](http://stackoverflow.com/questions/tagged/react-native). StackOverflow is amazing for Q&A: it has a reputation system, voting, the ability to mark a question as answered. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only. Will close this as this is really a question that should be asked on SO.
 add-label For Stack Overflow
+close
 
 /label (.*)
 add-label {match0}
 
+/no-reply
+comment Closing this issue as more information is needed to debug this and we haven't heard back from the author. Once there's more information we can reopen the issue.
+close
+
 /reopen
 comment Okay, reopening this issue.
 reopen

bots/IssueGuidelines.md

@@ -0,0 +1,37 @@
+Use the following tips when responding to GitHub issues.
+
+### An issue is a duplicate of another issue
+Comment e.g. `@facebook-github-bot /duplicate #123`. This will add a comment and close the issue.
+Example: #5977
+
+### An issue is a question
+StackOverflow is really good for Q&A. It has a reputation system and voting. Questions should absolutely be asked on StackOverflow rather than GitHub. However, to make this work we should hang out on StackOverflow every now and then and answer questions. A nice side effect is you'll get reputation for answering questions there rather than on GitHub.
+Comment `@facebook-github-bot /question` to close the issue.
+Examples: #6015, #6059, #6062
+
+### An issue is a question that's been answered
+Sometimes and issue has been resolved in the comments. Resolved issues should be closed.
+Comment `@facebook-github-bot /answered` to close it.
+Example: #6045
+
+### An issue needs more information
+It is impossible to understand and reproduce the issue without more information, e.g. a short code sample, screenshot.
+Do the following:
+- Explain what additional info you need to understand the issue
+- Comment `@facebook-github-bot /add-label Needs more information`
+Examples: #6056, #6008, #5491
+
+### An issue with label 'Needs more information' has been open for more than a week
+Comment mentioning the author asking if they plan to provide the additional information. If they don't come back close the issue using `@facebook-github-bot /no-reply`.
+Example: #6056
+
+### Want to add a label
+Add any relevant labels, for example 'Android', 'iOS'.
+Comment e.g. `@facebook-github-bot /add-label Android`.
+
+### Want to reopen a closed issue
+For example an issue was closed waiting for the author, the author replied and it turns out this is indeed a bug.
+Comment `@facebook-github-bot /reopen`
+
+### Commands for the bot
+When you mention the bot, it follows the commands defined in [IssueCommands.txt](https://github.com/facebook/react-native/blob/master/bots/IssueCommands.txt).