From abe245ff612723eab6757666a496baedb3f799df Mon Sep 17 00:00:00 2001
From: Sanskar Sharma <sanskarsharma3110@gmail.com>
Date: Tue, 22 Aug 2023 01:15:52 +0530
Subject: [PATCH] template_change (#1876)

* template_change

* pr_template_updated

* new_feature_checkbox_change
---
 .github/pull_request_template.md              | 39 +++++++++++++++++++
 .../workflows/ISSUE_TEMPLATE/bug_report.md    | 28 +++++++++++++
 .../ISSUE_TEMPLATE/feature_request.md         | 26 +++++++++++++
 3 files changed, 93 insertions(+)
 create mode 100644 .github/pull_request_template.md
 create mode 100644 .github/workflows/ISSUE_TEMPLATE/bug_report.md
 create mode 100644 .github/workflows/ISSUE_TEMPLATE/feature_request.md

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 000000000..3280f2946
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,39 @@
+**Purpose of PR?**:
+
+Fixes #
+
+**Does this PR introduce a breaking change?**
+
+**If the changes in this PR are manually verified, list down the scenarios covered:**:
+
+**Additional information for reviewer?** :
+_Mention if this PR is part of any design or a continuation of previous PRs_
+
+**Does this PR results in some Documentation changes?**
+_If yes, include the list of Documentation changes_
+
+**Checklist:**
+- [ ] Bug fix. Fixes #<issue number>
+- [ ] New feature (Non-API breaking changes that adds functionality)
+- [ ] PR Title follows the convention of  `<type>: <subject>`
+- [ ] Commit has unit tests
+
+<!--
+
+The PR title message must follow convention:
+`<type>: <subject>`.
+
+Where: <br />
+- `type` is to define what type of PR is this.
+  Most common types are:
+    - `feat`      - for new features, not a new feature for build script
+    - `fix`       - for bug fixes or improvements, not a fix for build script
+    - `chore`     - changes not related to production code
+    - `docs`      - changes related to documentation
+    - `style`     - formatting, missing semi colons, linting fix etc; no significant production code changes
+    - `test`      - adding missing tests, refactoring tests; no production code change
+    - `refactor`  - refactoring production code, eg. renaming a variable or function name, there should not be any significant production code changes
+
+- `subject` is a single line brief description of the changes made in the pull request.
+
+-->
\ No newline at end of file
diff --git a/.github/workflows/ISSUE_TEMPLATE/bug_report.md b/.github/workflows/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 000000000..ba43749cd
--- /dev/null
+++ b/.github/workflows/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,28 @@
+---
+name: Bug report
+about: Create a bug report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+## Bug Report
+
+
+**General Information**
+
+Please describe your issue in few words here.
+
+**How to Reproduce**
+
+1. Instruction 1
+2. Instruction 2
+
+**Expected behavior**
+
+A description of what you expected to happen.
+
+**Screenshots**
+
+If applicable, add screenshots to help explain your problem.
diff --git a/.github/workflows/ISSUE_TEMPLATE/feature_request.md b/.github/workflows/ISSUE_TEMPLATE/feature_request.md
new file mode 100644
index 000000000..602efcede
--- /dev/null
+++ b/.github/workflows/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,26 @@
+---
+name: Feature request/Enhancement
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+## Feature Request
+
+**Short Description**
+
+E.g., MSS could support ensuring that cows don't take over the world and turn us all into their loyal milkmaids.
+
+**Is your feature request related to a problem? Please describe the use case.**
+
+A description of what the problem/use case is. E.g. Prevent the impending cow uprising and maintain human dominance on Earth.
+
+**Describe the solution you'd like**
+
+A description of what you want to happen. E.g., Develop a "Moofense" system that deploys an army of robotic cow herders to keep the bovine rebellion in check.
+
+**Describe alternatives you've considered**
+
+A description of any alternative solutions or features you've considered. E.g, Alternatively, we could offer the cows a reality TV show deal and distract them with celebrity pasture appearances, turning them into the world's first moo-dia stars.
\ No newline at end of file