Update templates

.github/ISSUE_TEMPLATE/Bug_report.md

@@ -1,48 +1,23 @@
 ---
 name: Bug report
-about: Create a report to help us improve
-
+about: Create a report about something that is not working
 ---
 
-### Do you want to request a *feature* or report a *bug*?
-
-Bug
-
-### What did you do?
-
-<!--
-
-HOW TO WRITE A GOOD BUG REPORT?
-
-- Respect the issue template as much as possible.
-- The title should be short and descriptive.
-- Explain the conditions which led you to report this issue: the context.
-- The context should lead to something, an idea or a problem that you’re facing.
-- Remain clear and concise.
-- Format your messages to help the reader focus on what matters and understand the structure of your message, use Markdown syntax https://help.github.com/articles/github-flavored-markdown
-
--->
-
-### What did you expect to see?
-
-
-### What did you see instead?
-
-
-### Output of `git rev-parse HEAD`: (_What version of BaGet are you using?_)
-
-```
-(paste your output here)
-```
+### Describe the bug
+A clear and concise description of what the bug is.
 
-### What is your environment & configuration (arguments, platform, ...)?
+### To Reproduce
+Steps to reproduce the behavior:
+1. Using this version of BaGet '...'
+2. Run this code '....'
+3. With these arguments '....'
+4. See error
 
-<!--
-Add more configuration information here.
--->
+### Expected behavior
+A clear and concise description of what you expected to happen.
 
-### If applicable, please paste the log output in DEBUG level
+### Screenshots
+If applicable, add screenshots to help explain your problem.
 
-```
-(paste your output here)
-```
+### Additional context
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/Feature_request.md

@@ -1,24 +1,17 @@
 ---
 name: Feature request
 about: Suggest an idea for this project
-
 ---
 
-### Do you want to request a *feature* or report a *bug*?
-
-Feature
-
-### What did you expect to see?
-
-<!--
+### Is your feature request related to a problem? Please describe.
+A clear and concise description of what the problem is.
+Example. I'm am trying to do [...] but [...]
 
-HOW TO WRITE A GOOD ISSUE?
+### Describe the solution you'd like
+A clear and concise description of what you want to happen.
 
-- Respect the issue template as much as possible.
-- The title should be short and descriptive.
-- Explain the conditions which led you to report this issue: the context.
-- The context should lead to something, an idea or a problem that you’re facing.
-- Remain clear and concise.
-- Format your messages to help the reader focus on what matters and understand the structure of your message, use Markdown syntax https://help.github.com/articles/github-flavored-markdown
+### 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

@@ -1,31 +1,6 @@
-<!--
-PLEASE READ THIS MESSAGE.
+Summary of the changes (in less than 80 chars)
 
-HOW TO WRITE A GOOD PULL REQUEST?
+ * Detail 1
+ * Detail 2
 
-- Read the contributing guide: https://github.com/loic-sharma/BaGet/blob/master/CONTRIBUTING.md.
-- Make it small.
-- Do only one thing.
-- Avoid re-formatting.
-- Make sure the code builds.
-- Add tests.
-- Write useful descriptions and titles.
-- Address review comments in terms of additional commits.
-- Once approved, please squash your commits to avoid polluting the commit history.
--->
-
-### What does this PR do?
-
-<!-- A brief description of the change being made with this pull request. -->
-
-### Closes Issue(s)
-
-<!-- List here all the issues closed by this pull request. -->
-
-### Motivation
-
-<!-- What inspired you to submit this pull request? -->
-
-### Additional Notes
-
-<!-- Anything else we should know when reviewing? -->
+Addresses https://github.com/loic-sharma/BaGet/issues/123