chore: update issue template

Author: satya164

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,32 @@
+**Current Behavior**
+
+- What code are you running and what is happening?
+- Include a screenshot or video if it makes sense.
+
+**Expected Behavior**
+
+- What do you expect should be happening?
+- Include a screenshot or video if it makes sense.
+
+**How to reproduce**
+
+- You must provide a way to reproduce the problem. If you are having an issue with your machine or build tools, the issue belongs on another repository as that is outside of the scope of React Navigation.
+- Either re-create the bug on [Snack](https://snack.expo.io) or link to a GitHub repository with code that reproduces the bug.
+- Explain how to run the example app and any steps that we need to take to reproduce the issue from the example app.
+- Keep the repro code as simple as possible, with the minimum amount of code required to repro the issue.
+- Before reporting an issue, make sure you are on latest version of the package.
+
+**Your Environment**
+
+| software                     | version |
+| ---------------------------- | ------- |
+| iOS or Android               |
+| react-navigation             |
+| react-navigation-drawer      |
+| react-native-gesture-handler |
+| react-native-reanimated      |
+| react-native-screens         |
+| react-native                 |
+| expo                         |
+| node                         |
+| npm or yarn                  |

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,17 @@
+Please provide enough information so that others can review your pull request:
+
+**Motivation**
+
+Explain the **motivation** for making this change. What existing problem does the pull request solve?
+
+**Test plan**
+
+Demonstrate the code is solid. Example: the exact commands you ran and their output, screenshots / videos if the pull request changes UI.
+
+Make sure you test on both platforms if your change affects both platforms.
+
+The code must pass tests.
+
+**Code formatting**
+
+Look around. Match the style of the rest of the codebase. Run `yarn lint --fix` before committing.

.github/workflows/stale.yml

@@ -0,0 +1,16 @@
+name: "Close stale issues and pull requests"
+on:
+  schedule:
+  - cron: "0 0 * * *"
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/stale@v1
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        stale-issue-message: 'Hello 👋, this issue has been open for more than 2 months with no activity on it. If the issue is still present in the latest version, please leave a comment within 7 days to keep it open, otherwise it will be closed automatically. If you found a solution on workaround for the issue, please comment here for others to find. If this issue is critical for you, please consider sending a pull request to fix the issue.'
+        stale-pr-message: 'Hello 👋, this pull request has been open for more than 2 months with no activity on it. If you think this is still necessary with the latest version, please comment and ping a maintainer to get this reviewed, otherwise it will be closed automatically in 7 days.'
+        exempt-issue-label: 'Keep opened'
+        exempt-pr-label: 'Keep opened'