clarify PULL_REQUST_TEMPLATE.md & CONTRIBUTING.md #1291
8
.github/PULL_REQUEST_TEMPLATE.md
vendored
8
.github/PULL_REQUEST_TEMPLATE.md
vendored
@@ -1,8 +1,8 @@
|
||||
<!-- PLEASE READ OUR CONTRIBUTING GUIDELINES (https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md) BEFORE SUBMITTING -->
|
||||
<!-- PLEASE READ OUR CODE OF CONDUCT (https://github.com/privacytoolsIO/privacytools.io/blob/master/CODE_OF_CONDUCT.md) AND CONTRIBUTING GUIDELINES (https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md) BEFORE SUBMITTING -->
|
||||
|
||||
|
||||
## Description
|
||||
|
||||
![]() Oh and I wonder if we should also mention CODE_OF_CONDUCT.md on the top, but if we get a project that is full of hate, I guess we can refer to it separately. Oh and I wonder if we should also mention CODE_OF_CONDUCT.md on the top, but if we get a project that is full of hate, I guess we can refer to it separately.
![]() Hmm, I'm not sure but it doesn't hurt to add it as a comment at the top as a reminder. Hmm, I'm not sure but it doesn't hurt to add it as a comment at the top as a reminder.
![]() 👍 :+1:
|
||||
Resolves: #none <!-- The number of the issue that is resolved by this pull request. This should be number of the discussion issue. If there is none, feel free to delete this line -->
|
||||
Resolves: #none <!-- A link to the (discussion) issue resolved by this pull request. There must be a discussion issue here at GitHub, before a pull request of software/service suggestion can be considered for merging. -->
|
||||
|
||||
#### Check List <!-- Please add an x in each box below, like so: [x] -->
|
||||
![]() I think this is necessary if we are removing the "has associated discussion" part. I think this is necessary if we are removing the "has associated discussion" part.
|
||||
|
||||
@@ -10,9 +10,7 @@ Resolves: #none <!-- The number of the issue that is resolved by this pull reque
|
||||
|
||||
- [ ] I have listed the source code in [source_code.md](https://github.com/privacytoolsIO/privacytools.io/blob/master/source_code.md).
|
||||
|
||||
- [ ] The project is [open source software](https://en.wikipedia.org/wiki/Open-source_software).
|
||||
|
||||
- [ ] The project has an associated discussion: # <!-- issue number -->
|
||||
- [ ] The project is [Free Libre](https://en.wikipedia.org/wiki/Free_software) and/or [Open Source](https://en.wikipedia.org/wiki/Open-source_software) Software
|
||||
|
||||
* Netlify preview for the mainly edited page: <!-- link or Non Applicable? Edit this in afterwards -->
|
||||
![]() I think this is more clear formatting. I think this is more clear formatting.
|
||||
|
||||
|
Reference in New Issue
Block a user
First hint that we do want the discussion issue to exist.
I may want to check that wiki page and if there is a better one.
oops. Anyway the previous formatting was very unhelpful in my opinion as it just went to issue page and forced me to use search as no one (me included) never changed the link.
and I think
The
fits here better thanThis
, even if there is probably no practical difference.I would probably tidy this up a bit to:
Is this somewhat redundant due to already having a "Resolves"? Could we remove this line in favor of having the "Resolves"?
👍 I think I also need to clarify that discussion issue means software suggestion to distinguish it from discussions about news which we hoped to move to the forums.
I guess
Sorry, I have to mess it up, because if there are multiple issues,
Resolves: #1, #2
closes only#1
.No, I seem to be simplifying it more due to the other thread where I remove mentioning on the issue.