git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Inconsistent results from git rev-parse --show-toplevel

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 24, 2020, 19:59 UTC
Message-ID
<xmqqftg4zkvo.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<TU4PR8401MB111758B9513DD7D8B96CBFAAF90E0@TU4PR8401MB1117.NAMPRD84.PROD.OUTLOOK.COM>
"Crabtree, Andrew" <andrew.crabtree@hpe.com> writes:
> I ran into an issue where 'git rev-parse --show-toplevel' is reporting the current directory instead of the root of the repository.
> In my case I'm running it from within the pre-commit hook, and it seems like it might be related to GIT_DIR being set.

Running "git" with GIT_DIR exported (or "git --git-dir=<dir>") tells Git that it should not perform the usual "does this directory has a subdirectory .git that is a repository? If not, go one level up and repeat the check" repository discovery. Because the repository discovery serves the purpose of finding both the repository and the top of the working tree, disabling the discovery means you either need to tell Git where the top of the working tree is, or you are already at the top of the working tree by chdir()'ing to it.

Because you do not know where the top level is (otherwise you would not be asking "rev-parse --show-toplevel" about it), either is an option for you, but you can "unset GIT_DIR" to stop telling Git that it should not perform the repository discovery.

Previous: Crabtree, AndrewNext: Crabtree, Andrew
Message 2 of 8 in “Inconsistent results from git rev-parse --show-toplevel”
  1. Crabtree, AndrewJan 24, 2020
  2. Junio C HamanoJan 24, 2020
  3. Crabtree, AndrewJan 25, 2020
  4. Jeff KingJan 25, 2020
  5. Crabtree, AndrewJan 25, 2020
  6. Jeff KingJan 30, 2020
  7. Crabtree, AndrewJan 30, 2020
  8. Jeff KingFeb 14, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.