pimhwang
/
qTox
mirror of https://github.com/qTox/qTox.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Browse Source

docs(CONTRIBUTING.md): make more explicit what commit message needs 

By clearly stating what commit message needs to have.
Should help with commit messages that aren't really clear.
pull/3543/head
Zetok Zalbavar 9 years ago
parent
dca537954c
commit
78427b8e6b
No known key found for this signature in database
GPG Key ID: C953D3880212068A
1 changed files with 2 additions and 0 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 2
      CONTRIBUTING.md

2
CONTRIBUTING.md
Unescape View File

@ -39,6 +39,8 @@ Qt:
* Provide **screenshots** for UI related changes. * Provide **screenshots** for UI related changes.
* Keep your git commit history **clean** and **precise**. Commits like * Keep your git commit history **clean** and **precise**. Commits like
`xxx fixup` should not appear. `xxx fixup` should not appear.
* Commit message should state not only what has been changed, but also why a
change is needed.
* If your commit fixes a reported issue (for example #4134), add the following * If your commit fixes a reported issue (for example #4134), add the following
message to the commit `Fixes #4134.`. message to the commit `Fixes #4134.`.
[Here is an example](https://github.com/tux3/qTox/commit/87160526d5bafcee7869d6741a06045e13d731d5). [Here is an example](https://github.com/tux3/qTox/commit/87160526d5bafcee7869d6741a06045e13d731d5).

Write Preview
Loading…
Cancel
Save