sharpetronics/QGIS
1
0
Fork 0
mirror of https://github.com/qgis/QGIS.git synced 2025-02-23 00:02:38 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update pull request template and contribute.md

Browse Source
This commit is contained in:
Matthias Kuhn 2017-03-12 13:28:19 +01:00
parent 1d52846961
commit cd7b19c371
2 changed files with 10 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CONTRIBUTE.md → .github/CONTRIBUTE.md vendored
View File

@ -21,5 +21,5 @@ Getting your pull request merged
This is a volunteer project, so sometimes it may take a little while to merge
your pull request.
There is a [guide with hints for getting your pull requests merged](https://github.com/m-kuhn/QGIS-Website/blob/qtcreator.rst/source/site/getinvolved/development/git.rst#pull-requests)
There is a [guide with hints for getting your pull requests merged](https://www.qgis.org/en/site/getinvolved/development/qgisdevelopersguide/git.html#pull-requests)
in the developers guide.

21
.github/PULL_REQUEST_TEMPLATE.md vendored
View File

@ -1,18 +1,15 @@
## Description
Include a few sentences describing the overall goals for this pull request.
Include a few sentences describing the overall goals for this PR (pull request). If applicable also add screenshots.
## Checklist
All checklist items should be addressed before a QGIS maintainer will review the request:
> Reviewing is a process done by project maintainers, mostly on a volunteer basis. We try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items. Feel free to ask in a comment if you have troubles with any of them.
- [ ] I've read the [QGIS Coding Standards](https://www.qgis.org/en/site/getinvolved/development/qgisdevelopersguide/codingstandards.html) and this PR complies with them
- [ ] This PR passes all existing unit tests
- [ ] New unit tests have been added for core changes
- [ ] I've run the scripts/prepare-commit.sh script before each commit
- [ ] Commit messages are descriptive and explain the rationale for changes
- [ ] Commits which fix bugs include "fixes #11111" in the commit message
- [ ] Commits which add new features are tagged with \[FEATURE\] in the commit message
- [ ] Commits which change the UI or existing user workflows are tagged with \[needs-docs\] in the commit message
- [ ] Commits which fix bugs include `fixes #11111` in the commit message next to the description
- [ ] Commits which add new features are tagged with `[FEATURE]` in the commit message
- [ ] Commits which change the UI or existing user workflows are tagged with `[needs-docs]` in the commit message and containt sufficient information in the commit message to be documented
- [ ] I have read the [QGIS Coding Standards](https://www.qgis.org/en/site/getinvolved/development/qgisdevelopersguide/codingstandards.html) and this PR complies with them
- [ ] This PR passes all existing unit tests (test results will be reported by travis-ci after opening this PR)
- [ ] New unit tests have been added for core changes
- [ ] I have run [the `scripts/prepare-commit.sh` script](https://github.com/qgis/QGIS/blob/master/.github/CONTRIBUTE.md#contributing-to-qgis) before each commit