You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: index.html
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -108,11 +108,11 @@ <h2>How can you use GitGitGadget?</h2>
108
108
You might also want to read the <ahref="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 <ahref="https://github.com/git/git/blob/todo/MaintNotes">this note from Git's maintainer</a>.
109
109
</p><p>
110
110
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).
111
-
Any user who is already on that list can do that, by adding a comment to that Pull Request that says <tt>/allow <username></name></tt> (with your GitHub login name).
111
+
Any user who is already on that list can do that, by adding a comment to that Pull Request that says <code>/allow <username></name></code> (with your GitHub login name).
112
112
</p><p>
113
113
The Pull Request will trigger a few Checks, most importantly one that will build Git and run the test suite on the main platforms, to make sure that everything works as advertised.
114
114
</p><p>
115
-
Once everything is ready to go, add a comment to that Pull Request saying <tt>/submit</tt>.
115
+
Once everything is ready to go, add a comment to that Pull Request saying <code>/submit</code>.
116
116
This will trigger GitGitGadget (you can see the progress via the Check called "GitGitGadget PR Handler"): it will wrap your Pull Request into a nice bundle of mails in the format expected on the Git mailing list.
117
117
</p>
118
118
</div>
@@ -124,7 +124,7 @@ <h2>What happens after GitGitGadget sent the mails?</h2>
124
124
The Git developer community is globally distributed, so please wait a day or two for reviewer comments to trickle in before sending another iteration of your patch series (if needed).
125
125
</p><p>
126
126
In the case that a reviewer asks for changes, you should respond either acknowledging that you will make those changes or making an argument against the requested changes.
127
-
If your patches need to be revised, please use <tt>git rebase -i</tt> to do that, then force-push, then update the description of the Pull Request by adding a summary of the changes you made, and then issue another <tt>/submit</tt>.
127
+
If your patches need to be revised, please use <code>git rebase -i</code> to do that, then force-push, then update the description of the Pull Request by adding a summary of the changes you made, and then issue another <code>/submit</code>.
128
128
</p>
129
129
</div>
130
130
@@ -161,22 +161,22 @@ <h2>Should I use GitGitGadget on GitGitGadget's Git fork or on Git's GitHub mirr
161
161
<tdclass="tg-baqh">✅</td>
162
162
</tr>
163
163
<tr>
164
-
<tdclass="tg-0lax">Comment on the PR when the series is integrated into <tt>pu</tt>, <tt>next</tt>, <tt>master</tt> and <tt>maint</tt></td>
164
+
<tdclass="tg-0lax">Comment on the PR when the series is integrated into <code>pu</code>, <code>next</code>, <code>master</code> and <code>maint</code></td>
165
165
<tdclass="tg-baqh">✅</td>
166
166
<tdclass="tg-baqh">✅</td>
167
167
</tr>
168
168
<tr>
169
-
<tdclass="tg-0lax">Add a label to the PR when the series is integrated into <tt>pu</tt>, <tt>next</tt>, <tt>master</tt> and <tt>maint</tt></td>
169
+
<tdclass="tg-0lax">Add a label to the PR when the series is integrated into <code>pu</code>, <code>next</code>, <code>master</code> and <code>maint</code></td>
170
170
<tdclass="tg-baqh">✅</td>
171
171
<tdclass="tg-baqh">✅</td>
172
172
</tr>
173
173
<tr>
174
-
<tdclass="tg-0lax">Target <tt>pu</tt>, <tt>next</tt>, <tt>master</tt> and <tt>maint</tt></td>
174
+
<tdclass="tg-0lax">Target <code>pu</code>, <code>next</code>, <code>master</code> and <code>maint</code></td>
175
175
<tdclass="tg-baqh">✅</td>
176
176
<tdclass="tg-baqh">✅</td>
177
177
</tr>
178
178
<tr>
179
-
<tdclass="tg-0lax">Target any topic branch in the maintainer's fork, as well as <tt>git-gui/master</tt></td>
179
+
<tdclass="tg-0lax">Target any topic branch in the maintainer's fork, as well as <code>git-gui/master</code></td>
0 commit comments