Skip to content

Commit ec43d51

Browse files
committed
Using: add pointers to CodingGuidelines, gitworkflows, MaintNotes
1 parent 69c6152 commit ec43d51

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

index.html

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,8 @@ <h2>How can you use GitGitGadget?</h2>
5959
You can CC potential reviewers by adding a footer to the PR description with the following syntax:
6060
<pre>CC: Revi Ewer &lt;[email protected]&gt;, Ill Takalook &lt;[email protected]&gt;</pre>
6161
</p><p>
62-
You will also want to read <a href="https://git-scm.com/docs/SubmittingPatches">Git's guidelines</a> to make sure that your contributions are in the expected form.
62+
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>.
63+
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>.
6364
</p><p>
6465
The first time you use GitGitGadget, you need to be added to the list of users with permission to use GitGitGadget (this is a <i>very</i> simple anti-spam measure).
6566
Any user who is already on that list can do that, by adding a comment to that Pull Request that says <tt>/allow &lt;username&gt;</name></tt> (with your GitHub login name).

0 commit comments

Comments
 (0)