From: "Omri Sarig via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Omri Sarig <omri.sarig13@gmail.com>, Omri Sarig <omri.sarig13@gmail.com>
Subject: [PATCH v2] doc: add information regarding external commands
Date: Tue, 03 Mar 2026 17:12:05 +0000 [thread overview]
Message-ID: <pull.2220.v2.git.git.1772557925670.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.2220.git.git.1772479907062.gitgitgadget@gmail.com>
From: Omri Sarig <omri.sarig13@gmail.com>
Git supports running external commands in the user's PATH as if they
were built-in commands (see execv_dashed_external in git.c).
This feature was not fully documented in Git's user-facing
documentation.
This commit adds a short documentation of this feature, making it easier
for users to discover and use.
Signed-off-by: Omri Sarig <omri.sarig13@gmail.com>
---
doc: Add information regarding external commands
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2220%2Fomrisarig13%2Fexternal-commands-documentation-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2220/omrisarig13/external-commands-documentation-v2
Pull-Request: https://github.com/git/git/pull/2220
Range-diff vs v1:
1: b7e2b586c1 < -: ---------- doc: add information regarding external commands
-: ---------- > 1: 02841b66ea doc: add information regarding external commands
Documentation/git.adoc | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/git.adoc b/Documentation/git.adoc
index ce099e78b8..8bb3cb53f5 100644
--- a/Documentation/git.adoc
+++ b/Documentation/git.adoc
@@ -487,6 +487,13 @@ System
`$HOMEDRIVE$HOMEPATH` if both `$HOMEDRIVE` and `$HOMEPATH` exist;
otherwise `$USERPROFILE` if `$USERPROFILE` exists.
+`PATH`::
+ When a user runs 'git <command>' that is not part of the core Git programs
+ (installed in GIT_EXEC_PATH), 'git-<command>' that is runnable by the user
+ in a directory on `$PATH` is invoked. Argument passed after the command
+ name are passed as-is to the runnable program. These commands precedes
+ alias expansion.
+
The Git Repository
~~~~~~~~~~~~~~~~~~
These environment variables apply to 'all' core Git commands. Nb: it
base-commit: 2cc71917514657b93014134350864f4849edfc83
--
gitgitgadget
next prev parent reply other threads:[~2026-03-03 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 19:31 [PATCH] doc: add information regarding external commands Omri Sarig via GitGitGadget
2026-03-02 22:56 ` Junio C Hamano
2026-03-03 17:07 ` Omri Sarig
2026-03-03 17:12 ` Omri Sarig via GitGitGadget [this message]
2026-03-03 17:43 ` [PATCH v3] " Omri Sarig via GitGitGadget
2026-03-03 18:40 ` Junio C Hamano
2026-03-03 18:48 ` D. Ben Knoble
2026-03-03 20:11 ` Omri Sarig
2026-03-03 20:36 ` Junio C Hamano
2026-03-04 15:03 ` [PATCH v4] " Omri Sarig via GitGitGadget
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.2220.v2.git.git.1772557925670.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=omri.sarig13@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 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.