Mirroristas/CommunitySolidServer
2
0
Fork 0
mirror of https://github.com/CommunitySolidServer/CommunitySolidServer.git synced 2024-10-03 14:55:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Make pull request template more strict

Browse Source 
* Made pull request template more strict

* Update PULL_REQUEST_TEMPLATE.md
This commit is contained in:
Pieter Colpaert 2021-12-09 17:10:25 +01:00 committed by GitHub
parent 9c52011add
commit 48b29c5cc2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 17 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
.github/PULL_REQUEST_TEMPLATE.md vendored
View File

@ -1,15 +1,22 @@
#### 📁 Related issues
<!-- <!--
Things to check before submitting a pull request: Reference any relevant issues here. Closing keywords only have an effect when targeting the main branch. If there are no related issues, you must first create an issue through https://github.com/solid/community-server/issues/new/choose
* Label this PR with the correct semver label (if you have permission to do so). -->
#### ✍️ Description
<!-- Describe the relevant changes in this PR. Also add notes that might be relevant for code reviewers. -->
### ✅ PR check list
Before this pull request can be merged, a core maintainer will check whether
* [ ] this PR is labeled with the correct semver label
- semver.patch: Backwards compatible bug fixes. - semver.patch: Backwards compatible bug fixes.
- semver.minor: Backwards compatible feature additions. - semver.minor: Backwards compatible feature additions.
- semver.major: Breaking changes. This includes changing interfaces or configuration behaviour. - semver.major: Breaking changes. This includes changing interfaces or configuration behaviour.
* Target the correct branch. Patch updates can target main, other changes should target the latest versions/* branch. * [ ] the correct branch is targeted. Patch updates can target main, other changes should target the latest versions/* branch.
* Update the RELEASE_NOTES.md document in case of relevant feature or config changes. * [ ] the RELEASE_NOTES.md document in case of relevant feature or config changes.
-->
#### Related issues <!-- Try to check these to the best of your abilities before opening the PR -->
<!-- Reference any relevant issues here. Closing keywords only have an effect when targeting the main branch. -->
#### Description
<!-- Describe the relevant changes in this PR. Also add notes that might be relevant for code reviewers. -->