git/Documentation/MyFirstContribution.adoc, branch main

Merge branch 'sd/doc-my1c-api-config-reference-fix'

2026-02-13T21:39:26Z

Docfix. * sd/doc-my1c-api-config-reference-fix: doc: fix repo_config documentation reference

doc: fix repo_config documentation reference

2026-02-06T16:32:13Z

In MyFirstContribution.adoc, the link to the repo_config() documentation is invalid because the related documentation was moved to a different file. Replace the path for the repo_config() documentation from 'Documentation/technical/api-config.h' to 'config.h'. Signed-off-by: SoutrikDas Signed-off-by: Junio C Hamano

doc: MyFirstContribution: fix missing dependencies and clarify build steps

2026-01-12T20:24:02Z

Fix issues in the MyFirstContribution guide that can lead to confusion or test failures when following the documented steps. * Add missing header includes in code examples (environment.h and strbuf.h). * Correct manpage synopsis formatting to prevent failing documentation tests. * Specify the use of parallel test execution with -j$(nproc), noting that it runs tests using all available CPUs and may be adjusted. These updates improve documentation accuracy and make the first-time contributor journey smoother. Signed-off-by: Shreyansh Paliwal Signed-off-by: Junio C Hamano

MyFirstContribution: add note on confirming patches

2025-10-27T16:09:53Z

Add a note after the `git send-email` section explaining how contributors can confirm that their patches reached the mailing list by checking https://lore.kernel.org/git/. This helps contributors verify that their emails were successfully delivered. Signed-off-by: Queen Ediri Jessa Signed-off-by: Junio C Hamano

Merge branch 'ds/doc-ggg-pr-fork-clarify'

2025-09-02T15:21:27Z

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

doc: clarify which remotes can be used with GitGitGadget

2025-08-25T16:17:25Z

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 Acked-by: Elijah Newren Signed-off-by: Junio C Hamano

doc: add discord to ways of getting help

2025-08-20T16:58:15Z

Discord is a great way of receiving help for members of the community that are not on the mailing list or not familiar with Libera. Adding it to the official documentation will aid discoverability of it. The link is the same as the one at https://git-scm.com/community. Signed-off-by: Daniele Sassoli Signed-off-by: Junio C Hamano

docs: replace git_config to repo_config

2025-05-19T17:53:12Z

Since this document was written, the built-in API has been updated a few times, but the document was left stale. Adjust to the current best practices by calling repo_config() on the repository instance the subcommand implementation receives as a parameter, instead of calling git_config() that used to be the common practice. Signed-off-by: K Jayatheerth Signed-off-by: Junio C Hamano

docs: clarify cmd_psuh signature and explain UNUSED macro

2025-05-19T17:52:24Z

The sample program, as written, would no longer build for at least two reasons: - Since this document was first written, the convention to call a subcommand implementation has changed, and cmd_psuh() now needs to accept the fourth parameter, repository. - These days, compiler warning options for developers include one that detects and complains about unused parameters, so ones that are deliberately unused have to be marked as such. Update the old-style examples to adjust to the current practices, with explanations as needed. Signed-off-by: K Jayatheerth Signed-off-by: Junio C Hamano

docs: remove unused mentoring mailing list reference

2025-05-19T17:51:19Z

The git-mentoring group was initially created to help newcomers with their development itches. However, in practice, most of their questions were already being addressed directly on the mailing list, and contributors consistently received helpful responses there. Remove the mentoring group details from the Documentation. Signed-off-by: K Jayatheerth Signed-off-by: Junio C Hamano