Last active
August 29, 2015 14:11
-
-
Save AD7six/203427b37f985928e67e to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adding phpunit.xml.dist and bootstrap.php to be able to run the unit … | |
…tests. The tests itself are not yet fixed / updated. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adding phpunit.xml.dist and bootstrap.php | |
to be able to run the unit tests. The tests itself are not | |
yet fixed / updated. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Short (50 chars or less) summary of changes | |
More detailed explanatory text, if necessary. Wrap it to | |
about 72 characters or so. In some contexts, the first | |
line is treated as the subject of an email and the rest of | |
the text as the body. The blank line separating the | |
summary from the body is critical (unless you omit the body | |
entirely); tools like rebase can get confused if you run | |
the two together. | |
Further paragraphs come after blank lines. | |
- Bullet points are okay, too | |
- Typically a hyphen or asterisk is used for the bullet, | |
preceded by a single space, with blank lines in | |
between, but conventions vary here | |
http://git-scm.com/book/ch5-2.html |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment