ci: Add Github issue, pull request templates

Signed-off-by: Devaraj Ranganna <[email protected]>

Author: urutva

.github/CODEOWNERS

@@ -0,0 +1,37 @@
+# Each line is a file pattern followed by one or more owners.
+
+# These owners will be the default owners for everything in
+# the repo. Unless a later match takes precedence,
+# @global-owner1 and @global-owner2 will be requested for
+# review when someone opens a pull request.
+*      @FreeRTOS/pr-bar-raiser
+
+# Order is important; the last matching pattern takes the most
+# precedence. When someone opens a pull request that only
+# modifies JS files, only @js-owner and not the global
+# owner(s) will be requested for a review.
+# *.c FreeRTOS/pr-bar-raiser
+
+# You can also use email addresses if you prefer. They'll be
+# used to look up users just like we do for commit author
+# emails.
+# *.go [email protected]
+
+# In this example, @doctocat owns any files in the build/logs
+# directory at the root of the repository and any of its
+# subdirectories.
+# /build/logs/ @doctocat
+
+# The `docs/*` pattern will match files like
+# `docs/getting-started.md` but not further nested files like
+# `docs/build-app/troubleshooting.md`.
+# docs/*  [email protected]
+
+# In this example, @octocat owns any file in an apps directory
+# anywhere in your repository.
+# apps/ @octocat
+
+# In this example, @doctocat owns any file in the `/docs`
+# directory in the root of your repository and any of its
+# subdirectories.
+# /docs/ @doctocat

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,37 @@
+---
+name: Bug report
+about: Create a report to help us improve Arm Corstone-3xx FreeRTOS IoT
+       Reference. Please use this for confirmed bugs only. If you suspect
+       something it is best to first discuss it on the FreeRTOS forums linked
+       below.
+title: "[BUG]"
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A concise description of what the bug is. If possible, that is the code is not
+proprietary, please upload the code in a [GitHub fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo)
+such that we can reproduce the bug.
+
+**Host**
+- Host OS: [e.g. MacOS]
+- Version: [e.g. Mojave 10.14.6]
+
+**To Reproduce**
+- Use project ... and configure with ...
+- Run on ... and could observe ...
+
+**Expected behavior**
+A concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Additional context**
+Add any other context about the problem here.
+e.g. code snippet to reproduce the issue.
+e.g. stack trace, memory dump, debugger log, and many etc.
+
+<!-- For general inquiries, please post in [FreeRTOS forum](https://forums.FreeRTOS.org) for community support. -->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: FreeRTOS Community Support Forum
+    url: https://forums.freertos.org/
+    about: Please ask and answer questions about Arm Corstone-3xx FreeRTOS IoT Reference here.

.github/ISSUE_TEMPLATE/documentation-issue.md

@@ -0,0 +1,23 @@
+---
+name: Documentation issue
+about: Create a report to help us improve our documentation.
+title: "[DOC] "
+labels: ''
+assignees: ''
+
+---
+
+**Describe the issue**
+Please describe the issue and expected clarification in concise language.
+
+**Reference**
+Please attach the URL at which you are experiencing the issue.
+
+**Screenshot**
+If applicable, please attach screenshot.
+
+**Browser**
+- Browser: [e.g. Chrome]
+- Version: [e.g. 80.0.3987.132]
+
+<!-- For general inquiries, please post in [FreeRTOS forum](https://forums.FreeRTOS.org) for community support. -->

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,21 @@
+---
+name: Feature Request
+about: Suggest an idea for this project
+title: "[Feature Request] <replace with your title>"
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is.
+
+**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,22 @@
+<!--- Title -->
+
+Description
+-----------
+<!--- Describe your changes in detail. -->
+
+Test Steps
+-----------
+<!-- Describe the steps to reproduce. -->
+
+Checklist:
+----------
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+- [ ] I have tested my changes. No regression in existing tests.
+- [ ] I have modified and/or added unit-tests to cover the code changes in this Pull Request.
+
+Related Issue
+-----------
+<!-- If any, please provide issue ID. -->
+
+By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.