Pull request advice: Difference between revisions
Content added Content deleted
imported>Paulproteus No edit summary |
imported>Paulproteus No edit summary |
||
| Line 2: | Line 2: | ||
* We value of the quality of git commit log messages. Two great reads on that topic are: |
* We value of the quality of git commit log messages. Two great reads on that topic are: |
||
** [http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html A note about git commit messages] describes the technical details: 50 char summary, and so on |
** [http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html A note about git commit messages] describes the technical details: 50 char summary, and so on. |
||
** [http://www.codinghorror.com/blog/2011/02/how-to-write-without-writing.html How to write without writing] describes why writing is such an important skill for programmers. |
** [http://www.codinghorror.com/blog/2011/02/how-to-write-without-writing.html How to write without writing] describes why writing is such an important skill for programmers. |
||
Latest revision as of 00:13, 12 September 2013
This is just a collection of links that people submitting pull requests to OpenHatch code might find helpful.
- We value of the quality of git commit log messages. Two great reads on that topic are:
- A note about git commit messages describes the technical details: 50 char summary, and so on.
- How to write without writing describes why writing is such an important skill for programmers.
- We try to only add code when we can think of a reason we need it. See "You Ain't Gonna Need it", documented e.g. on Wikipedia.