Do not use multiple PR templates (#423)

Github handles multiple PR templates only with url params
and we wanted it to display as issues
The result is no template is used, so back one step to single template

Signed-off-by: Nicolas MASSART <nicolas.massart@consensys.net>

.github/PULL_REQUEST_TEMPLATE/Content.md

@@ -1,43 +0,0 @@
----
-name: Content pull request
-about: Propose a change on the content in this documentation.
-title: ''
-
----
-
-<!-- **IMPORTANT: this is only for documentation content changes.**
-If you want to suggest a change to the tools, CI and build process, create a DocOps pull request.
-
-**Before pushing any commit in your pull request, make sure that you:**
-
-- read the [contribution guidelines](https://wiki.hyperledger.org/display/BESU/Contributing+to+documentation).
-- [signed all commits of for the DCO](https://wiki.hyperledger.org/display/BESU/DCO).
-- have [tested your changes locally](https://wiki.hyperledger.org/display/BESU/MkDocs+And+Markdown+Guide#MkDocsAndMarkdownGuide-PreviewTheDocumentation) before submitting them to the community for review. -->
-
-## Describe the change
-
-<!-- A clear and concise description of what this PR changes in the content. -->
-
-## Issue fixed
-
-<!-- Except for minor changes (typos, commas) it's required to have a Github issue linked to your
-pull request.
-
-Use the following to make Github close the issue automatically when merging the PR:
-
-fixes #{your issue number}
-
-If you don't want to close the issue, use:
-
-see #{your issue number} -->
-
-## Testing
-
-<!-- Steps to follow to review your changes.
-
-Don't forget to test your change locally before any review request. -->
-
-## Screenshots / recording
-
-<!-- If it helps understanding your change,
-don't hesitate to link an annotated screenshot or a small demo video. -->

.github/pull_request_template.md

@@ -1,23 +1,12 @@
----
-name: DocOps pull request
-about: Propose a change on this documentation tools.
-title: ''
-labels: DocOps
-
----
-
-<!-- **IMPORTANT: this is only for documentation tools changes.**
-If you want to suggest a change to the content, create a content pull request.
-
 **Before pushing any commit in your pull request, make sure that you:**
 
-- read the [contribution guidelines](https://wiki.hyperledger.org/display/BESU/Contributing+to+documentation).
-- [signed all commits of for the DCO](https://wiki.hyperledger.org/display/BESU/DCO).
-- have [tested your changes locally](https://wiki.hyperledger.org/display/BESU/MkDocs+And+Markdown+Guide#MkDocsAndMarkdownGuide-PreviewTheDocumentation) before submitting them to the community for review. -->
+- [ ] read the [contribution guidelines](https://wiki.hyperledger.org/display/BESU/Contributing+to+documentation).
+- [ ] [signed all commits of for the DCO](https://wiki.hyperledger.org/display/BESU/DCO).
+- [ ] have [tested your changes locally](https://wiki.hyperledger.org/display/BESU/MkDocs+And+Markdown+Guide#MkDocsAndMarkdownGuide-PreviewTheDocumentation) before submitting them to the community for review. -->
 
 ## Describe the change
 
-<!-- A clear and concise description of what this PR changes in the doc tools. -->
+<!-- A clear and concise description of what this PR changes in the documentation. -->
 
 ## Issue fixed
 
@@ -25,16 +14,20 @@ If you want to suggest a change to the content, create a content pull request.
 pull request.
 
 Use the following to make Github close the issue automatically when merging the PR:
-
 fixes #{your issue number}
+If multiple issues are involved, use one line for each issue.
 
 If you don't want to close the issue, use:
-
 see #{your issue number} -->
 
-## Impacted parts
+## Impacted parts <!-- check as many boxes as needed -->
+
+### For content changes
+
+- [ ] Doc content
+- [ ] Doc pages organisation
 
-<!-- Indicate what parts are impacted by your changes (insert X instead of space between [ ]): -->
+### For tools changes
 
 - [ ] CircleCI workflow
 - [ ] Build and QA tools (lint, vale,…)
@@ -47,7 +40,7 @@ see #{your issue number} -->
 
 ## Testing
 
-Steps to follow to review and test your changes.
+<!-- Steps to follow to review and test your changes. -->
 
 ## Screenshots / recording