While troubleshooting commit hooks on a Linux server, you find that Git is executing hooks from an unexpected directory even though your personal ~/.gitconfig sets core.hooksPath=$HOME/.githooks. You need to confirm both the value Git will use and the exact configuration file that supplied it. Which single Git command accomplishes this?
Adding the --show-origin option tells Git to print the origin type and the absolute path of the configuration file that provided each value. Therefore, git config --show-origin core.hooksPath reveals the effective path together with the file (for example, .git/config or /etc/gitconfig) that overrides your personal setting. Commands such as --get or --list can display the value but omit the file name, --show-scope displays only the scope (local, global, system), and combining --list --show-origin with grep requires an additional shell command, so it is not a single Git command as requested.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What does the `--show-origin` option in Git do?
Open an interactive chat with Bash
What is the difference between `core.hooksPath` and the default location for Git hooks?
Open an interactive chat with Bash
How do configuration file scopes (local, global, system) affect Git settings?
Open an interactive chat with Bash
CompTIA Linux+ XK0-006 (V8)
Automation, Orchestration, and Scripting
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access