From 7edca3eb0406b4358166a1ecaf85dab6a83a493b Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Mon, 29 Oct 2018 12:16:39 -0700 Subject: [PATCH] doc: pull request guidelines tweak [ci skip] --- .github/PULL_REQUEST_TEMPLATE/pull-request.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE/pull-request.md b/.github/PULL_REQUEST_TEMPLATE/pull-request.md index 82c69d131..768483246 100644 --- a/.github/PULL_REQUEST_TEMPLATE/pull-request.md +++ b/.github/PULL_REQUEST_TEMPLATE/pull-request.md @@ -1,6 +1,7 @@ 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, ensuring hledger remains a high quality, maintainable product. 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, 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. Don't tackle too much at once. Mention any #ISSUENOs addressed.