From: "Rhythm Narula via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Rhythm Narula <rhythm.narula26@gmail.com>,
Rhythm-26 <rhythm.narula26@gmail.com>
Subject: [PATCH v2] docs: mention source of tasks in MyFirstContribution
Date: Tue, 14 Jan 2025 08:48:57 +0000 [thread overview]
Message-ID: <pull.1867.v2.git.git.1736844538005.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1867.git.git.1736080517950.gitgitgadget@gmail.com>
From: Rhythm-26 <rhythm.narula26@gmail.com>
MyFirstContribution guide lacks clear guidance on where to access
list of bugs or feature requests. Improve visibility for contributors
on where to find open issues and features that need attention.
CC: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Rhythm-26 <rhythm.narula26@gmail.com>
---
docs: updates MyFirstContribution guide to refer current bugs and
feature requests
cc: Carlo Marcelo Arenas Belón carenas@gmail.com cc: Emily Shaffer
nasamuffin@google.com
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1867%2FRhythm-26%2FupdateContirbutingDocumentation-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1867/Rhythm-26/updateContirbutingDocumentation-v2
Pull-Request: https://github.com/git/git/pull/1867
Range-diff vs v1:
1: d3e264b1cc5 ! 1: d1e83439133 docs: update contributing guide to refer current bugs and feature requests
@@ Metadata
Author: Rhythm-26 <rhythm.narula26@gmail.com>
## Commit message ##
- docs: update contributing guide to refer current bugs and feature requests
+ docs: mention source of tasks in MyFirstContribution
- The contributing guide is updated to include references to the current
- open bugs and feature requests. This update aims to improve visibility
- for contributors on where to find open issues and features that need
- attention.
+ MyFirstContribution guide lacks clear guidance on where to access
+ list of bugs or feature requests. Improve visibility for contributors
+ on where to find open issues and features that need attention.
CC: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Rhythm-26 <rhythm.narula26@gmail.com>
@@ Documentation/MyFirstContribution.txt: of invocation during users' typical daily
+:mailinglist: git+subscribe@vger.kernel.org
+
-+Here's where you can find bugs and feature requests existing in the system:
++For future reference, here's where you can find bugs and feature requests existing in the system:
+
+ - Git uses a mailing list for discussion on bugs, features and patches. Search for relevant topics or tagged issues
-+ like #leftoverbits in the archives: https://lore.kernel.org/git/
-+ - Unofficial bug trackers - https://github.com/gitgitgadget/git/issues, https://git.issues.gerritcodereview.com/
++ like #leftoverbits in the archives: https://lore.kernel.org/git/. If you encounter a bug, have a feature request,
++ or wish to discuss or share suggestions, please use the mailing list. You can find more details in the <<getting-help>> section.
++ - Unofficial bug trackers - https://github.com/gitgitgadget/git/issues [NOTE: This is for feature requests only],
++ https://git.issues.gerritcodereview.com/
+
[[setup-workspace]]
=== Set Up Your Workspace
Documentation/MyFirstContribution.txt | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/MyFirstContribution.txt b/Documentation/MyFirstContribution.txt
index e41654c00a6..630a68b650c 100644
--- a/Documentation/MyFirstContribution.txt
+++ b/Documentation/MyFirstContribution.txt
@@ -109,6 +109,16 @@ of invocation during users' typical daily workflow.
(We've seen some other effort in this space with the implementation of popular
commands such as `sl`.)
+:mailinglist: git+subscribe@vger.kernel.org
+
+For future reference, here's where you can find bugs and feature requests existing in the system:
+
+ - Git uses a mailing list for discussion on bugs, features and patches. Search for relevant topics or tagged issues
+ like #leftoverbits in the archives: https://lore.kernel.org/git/. If you encounter a bug, have a feature request,
+ or wish to discuss or share suggestions, please use the mailing list. You can find more details in the <<getting-help>> section.
+ - Unofficial bug trackers - https://github.com/gitgitgadget/git/issues [NOTE: This is for feature requests only],
+ https://git.issues.gerritcodereview.com/
+
[[setup-workspace]]
=== Set Up Your Workspace
base-commit: 1b4e9a5f8b5f048972c21fe8acafe0404096f694
--
gitgitgadget
next prev parent reply other threads:[~2025-01-14 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 12:35 [PATCH] docs: update contributing guide to refer current bugs and feature requests Rhythm Narula via GitGitGadget
2025-01-08 10:43 ` Carlo Marcelo Arenas Belón
2025-01-08 20:40 ` Emily Shaffer
2025-01-14 8:48 ` Rhythm Narula via GitGitGadget [this message]
2025-01-14 17:24 ` [PATCH v2] docs: mention source of tasks in MyFirstContribution Junio C Hamano
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.1867.v2.git.git.1736844538005.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=rhythm.narula26@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).