lunny/git-lfs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

CONTRIBUTING: encourage a rationale in the pull request

Browse Source 
Sometimes we get pull requests that have no description or rationale.
This makes it hard for maintainers to evaluate why the pull request is
needed and what problems it is intended to solve. Encourage users to
provide some explanation in the pull request and hinting that they may
use part (or all) of their good commit message to accomplish this goal.
This commit is contained in:
brian m. carlson 2019-05-30 14:41:52 +00:00
parent 084fcb9ed7
commit ff57c2e692
No known key found for this signature in database
GPG Key ID: 2D0C9BC12F82B3A1
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CONTRIBUTING.md
View File

@ -71,6 +71,8 @@ Here are a few things you can do that will increase the likelihood of your pull
would like to make that are not dependent upon each other, consider submitting
them as separate pull requests.
* Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
* Explain the rationale for your change in the pull request. You can often use
part of a good commit message as a starting point.
## Building