Merge pull request #8 from phil-blain/single-patch-pr

Instruct readers to drop PR description for single commit PRs

Author: dscho

.gitattributes

@@ -1,4 +1,4 @@
 .gitattributes eol=lf
-*.html eol=lf
+*.html eol=lf diff=html
 *.svg eol=lf
 *.png binary

index.html

@@ -100,10 +100,14 @@ <h2>How can you use GitGitGadget?</h2>
 				So you cloned <a href="https://github.com/git/git">https://github.com/git/git</a> and implemented a bug fix or a new feature?
 				And you already pushed it to your own fork?
 				Good, now is the time to direct your web browser to <a href="https://github.com/gitgitgadget/git">https://github.com/gitgitgadget/git</a> (or to <a href="https://github.com/git/git">https://github.com/git/git</a> ) and to open a Pull Request.
-				Please make sure to use a descriptive Pull Request title and description; GitGitGadget will use these as the subject and body of the cover letter (check out the <a href="https://git-scm.com/docs/MyFirstContribution">MyFirstContribution</a> tutorial if you are not familiar with this terminology).
-				You can CC potential reviewers by adding a footer to the PR description with the following syntax:
-			</p><p>
-				<code>CC: Revi Ewer &lt;[email protected]&gt;, Ill Takalook &lt;[email protected]&gt;</code>
+				A few things to note about a GitGitGadget Pull Request:
+				<ul>
+					<li>Please make sure to use a descriptive title and description; GitGitGadget will use these as the subject and body of the cover letter (check out the <a href="https://git-scm.com/docs/MyFirstContribution#cover-letter">MyFirstContribution</a> tutorial if you are not familiar with this terminology).</li>
+					<li>If your pull request consist of a single commit, leave the pull request description empty, as your commit message itself should be enough to explain the rationale for your changes.</li>
+					<li>You can CC potential reviewers by adding a footer to the PR description with the following syntax:</br>
+					<code>CC: Revi Ewer &lt;[email protected]&gt;, Ill Takalook &lt;[email protected]&gt;</code>
+					</li>
+				</ul>
 			</p><p>
 				You will also want to read <a href="https://git-scm.com/docs/SubmittingPatches">Git's contribution guidelines</a> to make sure that your contributions are in the expected form, as well as the project's <a href="https://github.com/git/git/blob/master/Documentation/CodingGuidelines">coding guidelines</a>.
 				You might also want to read the <a href="https://git-scm.com/docs/gitworkflows">gitworkflows</a> manual page to understand how your contributions will be integrated in Git's repository, as well as <a href="https://github.com/git/git/blob/todo/MaintNotes">this note from Git's maintainer</a>.