slaesvuo/hledger
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc: pull request guidelines tweak

Browse Source 
[ci skip]
This commit is contained in:
Simon Michael 2018-10-29 12:16:39 -07:00
parent efb332cc23
commit 7edca3eb04
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
.github/PULL_REQUEST_TEMPLATE/pull-request.md vendored
View File

@ -1,6 +1,7 @@
Thanks for your pull request! Your work is appreciated. Thanks for your pull request! Your work is appreciated.
We like to merge as quickly as possible without endangering the project's long term health. Here are some tips for contributing pull requests to hledger.
We like to merge as quickly as possible without endangering the project's long term health.
Much valuable design, quality control, and knowledge sharing happens at merge time, Much valuable design, quality control, and knowledge sharing happens at merge time,
ensuring hledger remains a high quality, maintainable product. ensuring hledger remains a high quality, maintainable product.
Some PRs will require substantial review, discussion, changes, or re-submission. Some PRs will require substantial review, discussion, changes, or re-submission.
@ -12,8 +13,6 @@ Treat it as a golden opportunity to collaborate with experts,
share and receive knowledge, refine your design/documentation/code, share and receive knowledge, refine your design/documentation/code,
and improve real-world development/communication skills. and improve real-world development/communication skills.
Here are some tips to optimise your pull requests and minimise the risk of waste.
A PR should have a clear purpose, documented in its description. A PR should have a clear purpose, documented in its description.
Don't tackle too much at once. Don't tackle too much at once.
Mention any #ISSUENOs addressed. Mention any #ISSUENOs addressed.