From: Abdalrhman Mohamed <eng.abdalrhman.abdalmonem@gmail.com>
To: git@vger.kernel.org
Cc: Abdalrhman Mohamed <Eng.Abdalrhman.Abdalmonem@gmail.com>
Subject: [PATCH] .github/CONTRIBUTING.md: fix broken link to SubmittingPatches
Date: Sat, 31 Jan 2026 18:14:01 +0200 [thread overview]
Message-ID: <20260131161401.48693-1-Eng.Abdalrhman.Abdalmonem@gmail.com> (raw)
The link to SubmittingPatches documentation was pointing to a
non-existent 'Documentation' branch. Correct it to point to the
'master' branch so that new contributors on GitHub can find the
submission guidelines.
Signed-off-by: Abdalrhman Mohamed <Eng.Abdalrhman.Abdalmonem@gmail.com>
---
.github/CONTRIBUTING.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
index c8755e38de..e5d696fd42 100644
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -10,7 +10,7 @@ conveniently send your Pull Requests commits to our mailing list.
Please read ["A note from the maintainer"](https://git.kernel.org/pub/scm/git/git.git/plain/MaintNotes?h=todo)
to learn how the Git project is managed, and how you can work with it.
-In addition, we highly recommend you to read [our submission guidelines](../Documentation/SubmittingPatches).
+In addition, we highly recommend you to read [our submission guidelines](https://github.com/git/git/blob/master/Documentation/SubmittingPatches).
If you prefer video, then [this talk](https://www.youtube.com/watch?v=Q7i_qQW__q4&feature=youtu.be&t=6m4s)
might be useful to you as the presenter walks you through the contribution
--
2.25.1
next reply other threads:[~2026-01-31 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 16:14 Abdalrhman Mohamed [this message]
2026-01-31 19:50 ` [PATCH] .github/CONTRIBUTING.md: fix broken link to SubmittingPatches Junio C Hamano
2026-01-31 20:55 ` Todd Zullinger
2026-02-01 0:26 ` [PATCH v2] .github/CONTRIBUTING.md: link to SubmittingPatches on git-scm.com Abdalrhman Mohamed
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=20260131161401.48693-1-Eng.Abdalrhman.Abdalmonem@gmail.com \
--to=eng.abdalrhman.abdalmonem@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox