Add Checklist to PRs #1041
1
.github/PULL_REQUEST_TEMPLATE.md
vendored
1
.github/PULL_REQUEST_TEMPLATE.md
vendored
@ -7,7 +7,6 @@ Resolves: #none <!-- The number of the issue that is resolved by this pull reque
|
|||||||
<!--
|
<!--
|
||||||
## Screenshots
|
## Screenshots
|
||||||
|
|||||||
|
|
||||||
Please add screenshots if applicable
|
|
||||||
-->
|
-->
|
||||||
|
|
||||||
#### Check List <!-- Please add an x in each box below, like so: [x] -->
|
#### Check List <!-- Please add an x in each box below, like so: [x] -->
|
||||||
|
Reference in New Issue
Block a user
I think this is reduntant as when you open a PR, GitHub suggests you on the right to read the contributing guidelines. It also appears somewhat formal to me.
I am not sure if this is that good idea as it could easily cause a merge conflict if multiple users were submitting PRs to add multiple apps/services simultaneously. I think it should possibly be something for a team member to update (but it needs a PR with approval)? Ideas @BurungHantu1605 ?
I think this should be "Project is preferably..."
I wonder if this could be removed as Netlify handles that?
AFAIK it will only cause a merge conflict if people edit the same line, which seems unlikely since they'll likely be editing different sections of the file. But in any case merge conflicts are relatively easy to solve when a team member merges them. I would however make the following grammatical changes:
I think this is fine to include if we're doing this, because it means people need to affirm that they have read it directly.
I would add instructions for those unfamiliar with Markdown.
fixed in latest commit.
Thx
Software must actually be free software:
https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md#software
But, ya that description makes more sense.