Skip to content

Commit 71aea64

Browse files
committed
Merge branch 'ds/doc-ggg-pr-fork-clarify' into next
Update the instruction to use of GGG in the MyFirstContribution document to say that a GitHub PR could be made against `git/git` instead of `gitgitgadget/git`. * ds/doc-ggg-pr-fork-clarify: doc: clarify which remotes can be used with GitGitGadget
2 parents 1e63ebf + 37001cd commit 71aea64

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

Documentation/MyFirstContribution.adoc

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -917,10 +917,13 @@ Now you should be able to go and check out your newly created branch on GitHub.
917917
=== Sending a PR to GitGitGadget
918918

919919
In order to have your code tested and formatted for review, you need to start by
920-
opening a Pull Request against `gitgitgadget/git`. Head to
921-
https://github.com/gitgitgadget/git and open a PR either with the "New pull
922-
request" button or the convenient "Compare & pull request" button that may
923-
appear with the name of your newly pushed branch.
920+
opening a Pull Request against either `gitgitgadget/git` or `git/git`. Head to
921+
https://github.com/gitgitgadget/git or https://github.com/git/git and open a PR
922+
either with the "New pull request" button or the convenient "Compare & pull
923+
request" button that may appear with the name of your newly pushed branch.
924+
925+
The differences between using `gitgitgadget/git` and `git/git` as your base can
926+
be found [here](https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror)
924927

925928
Review the PR's title and description, as they're used by GitGitGadget
926929
respectively as the subject and body of the cover letter for your change. Refer

0 commit comments

Comments
 (0)