All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniele Sassoli via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Daniele Sassoli <danielesassoli@gmail.com>,
	Daniele Sassoli <danielesassoli@gmail.com>
Subject: [PATCH] doc:clarify which remotes can be used when contributing
Date: Tue, 19 Aug 2025 19:14:42 +0000	[thread overview]
Message-ID: <pull.2034.git.git.1755630882418.gitgitgadget@gmail.com> (raw)

From: Daniele Sassoli <danielesassoli@gmail.com>

The docs mostly point to using git/git as one's remote, however, when it
comes to Sending a PR to GitGitGadget section, the reader is told to use
gitgitgadget/git, with no mention of git/git, potentially leading to
some confusion.

Clarify that both gitgitgadget/git and git/git can be used, albeit with
some differences.

Signed-off-by: Daniele Sassoli <danielesassoli@gmail.com>
---
    doc:clarify which remotes can be used when contributing

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2034%2FDanieleSassoli%2Fclarify-remote-to-use-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2034/DanieleSassoli/clarify-remote-to-use-v1
Pull-Request: https://github.com/git/git/pull/2034

 Documentation/MyFirstContribution.adoc | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc
index aca7212cfe2..d014c5c36e1 100644
--- a/Documentation/MyFirstContribution.adoc
+++ b/Documentation/MyFirstContribution.adoc
@@ -908,10 +908,16 @@ Now you should be able to go and check out your newly created branch on GitHub.
 === Sending a PR to GitGitGadget
 
 In order to have your code tested and formatted for review, you need to start by
-opening a Pull Request against `gitgitgadget/git`. Head to
+opening a Pull Request against either `gitgitgadget/git` or `git/git`, depending
+on which mirror you initially cloned from. Head to
 https://github.com/gitgitgadget/git and open a PR either with the "New pull
 request" button or the convenient "Compare & pull request" button that may
 appear with the name of your newly pushed branch.
+If you're using https://github.com/git/git as your remote, you will need to
+open the pull-request from your fork, selecting `git/git` as base.
+
+The differences between using `gitgitgadget/git` and `git/git` as your base can
+be found [here](https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror)
 
 Review the PR's title and description, as they're used by GitGitGadget
 respectively as the subject and body of the cover letter for your change. Refer

base-commit: c44beea485f0f2feaf460e2ac87fdd5608d63cf0
-- 
gitgitgadget

             reply	other threads:[~2025-08-19 19:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-19 19:14 Daniele Sassoli via GitGitGadget [this message]
2025-08-19 21:19 ` [PATCH] doc:clarify which remotes can be used when contributing Junio C Hamano
2025-08-20 14:07   ` Daniele Sassoli
2025-08-20 21:16     ` Junio C Hamano
2025-08-22  9:14       ` Daniele Sassoli
2025-08-22 17:56         ` Junio C Hamano
2025-08-22 18:45 ` Elijah Newren
2025-08-23  9:12 ` [PATCH v2] " Daniele Sassoli via GitGitGadget
2025-08-25 15:39   ` Elijah Newren
2025-08-25 16:21     ` Junio C Hamano
2025-08-26  6:50       ` Daniele Sassoli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pull.2034.git.git.1755630882418.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=danielesassoli@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.