chore: updating the ISSUE_TEMPLATE for contributions.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,52 @@
+---
+name: Bug report
+about: Create a report to help us improve
+---
+
+<!--
+Before filling out an issue:
+1. A bug means that there is something broken or outside expectations in react-native-elements. If you only need help writing your own components, check out the [Slack channel](https://react-native-elements-slack.herokuapp.com/) FIRST.
+2. If any section is left blank, there is a high possibility that the ticket will be closed. If you want your issue to get solved, you need to fill out ALL of the below fields. Otherwise, the ticket will likely be closed as not providing enough info.
+-->
+
+**Explain what you did (Required)**
+
+<!-- What you were trying to accomplish. -->
+
+**Expected behavior (Required)**
+
+<!-- A clear and concise description of what you expected to happen. -->
+
+**Describe the bug (Required)**
+
+<!--  A clear and concise description of what the bug is. -->
+
+**To Reproduce (Required)**
+
+> We highly recommend that you re-create the bug on [Snack](https://snack.expo.io). If not, list the steps that a reviewer can take to reproduce the behaviour:
+
+<!--
+Example:
+
+```bash
+# Snack
+https://snack.expo.io/xxx
+
+# Steps
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+```
+-->
+
+**Screenshots (Required)**
+
+<!-- If applicable, add screenshots to help explain your problem. -->
+
+**Your Environment (Required):**
+
+| software              | version |
+| --------------------- | ------- |
+| react-native-elements |         |
+| react-native          |         |

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,20 @@
+---
+name: Feature Request
+about: Suggest an idea or enhancement for this project
+---
+
+**Is your feature request related to a problem? Please Describe.**
+
+<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
+
+**Describe the solution you'd like**
+
+<!-- A clear and concise description of what you want to happen. -->
+
+**Describe alternatives you've considered**
+
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
+
+**Additional context**
+
+<!-- Add any other context or screenshots about the feature request here. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,20 @@
+<!-- Thanks for submitting a pull request! Please provide enough information so that others can review your pull request. -->
+
+**What kind of change does this PR introduce?**
+
+<!-- E.g. a bugfix, feature, refactoring, build related change, etc… -->
+
+**Did you add tests for your changes?**
+
+**If relevant, did you update the documentation?**
+
+**Summary**
+
+<!-- Explain the **motivation** for making this change. What existing problem does the pull request solve? -->
+<!-- Try to link to an open issue for more information. -->
+
+**Does this PR introduce a breaking change?**
+
+<!-- If this PR introduces a breaking change, please describe the impact and a migration path for existing applications. -->
+
+**Other information**