Patch1

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+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,35 @@
+## Description ##
+(Brief description on what this PR is about)
+
+## If it is solving an issue, mention the issue number
+
+## Language ##
+(enter x where it is correct for you)
+- [] C
+- [] C++
+- [] Java
+- [] Python
+
+## Language - Branch mapping
+| Lang      | The branch to which you are making the PR|
+| ----------- | ----------- |
+| C      | C       |
+| C++   | master        |
+| Java   | Java        |
+| Python   | Python        |
+
+## Does your PR satisfy this mapping?
+- [] Yes
+- [] No
+
+## Checklist ##
+### Essentials ###
+- [ ] Changes are complete (i.e. I finished coding on this PR)
+- [ ] Code is well-documented
+
+### Changes ###
+- [ ] Feature1
+- [ ] Feature2
+
+## Comments ##
+- Interesting edge cases to note here

CONTRIBUTING.md

@@ -1,4 +1,16 @@
-# How to Collaborate:
+# Contributions
+
+## Making a PR ##
+
+Make sure that you fill out the relevant details in the PR.
+
+## Guidelines for Merging
+
+The PR which will be having the specific file name as given in the issue, the one whose commit descriptions are relevant, and the code is readable, would be merged.
+
+For docs, make sure that you use markdown syntax. Checkout these links: [Markdown Guide](https://www.markdownguide.org/), [Markdown Cheat-Sheet](https://www.markdownguide.org/cheat-sheet/).
+
+## How to Collaborate:
 
 1. Fork the repository to your own GitHub account.
 
@@ -21,17 +33,14 @@ $ git add <filename>
 ```
 
 5. Commit you changes with a commit message containing your name, file(s) worked upon, changes added.
-```
-$ git commit -m "Name| files| Changes"
-```
 
 6. Push changes to your forked repository
 ```
 $ git push -u origin branchname
 ```
 7. Create a pull request to the upstream repository.
 
-# Synchronize forked repository with Upstream repository
+## Synchronize forked repository with Upstream repository
 
 1. Create upstream as our repository
 ```