禁用有关分离的HEAD的警告

Question

在git中,如果你直接签出提交,你会得到一个很大的警告:

"You are in 'detached HEAD' state. You can look around ..."

没关系 - 我打算处于独立的HEAD状态.但是我在脚本中使用它,我不希望在输出日志中出现此警告,但我确实需要正常输出.

我现在的"丑陋"解决方法是两次运行相同的命令,首先用-q隐藏警告,再用一次得到正常输出:HEAD is now at deadbeef... Message因为警告只打印一次.

警告是否可以禁用,以便我可以避免解决方法或解析输出？

Answer 1

无耻地复制mjs的评论,将其作为答案自行发布:

git -c advice.detachedHead=false checkout <refspec>

该-c advice.detachedHead=false参数将允许您在不必更改全局配置的情况下禁止警告.它仅适用于执行的命令.这是可以抑制的所有建议的列表.

Answer 2

您有此任务的配置:

通过将config值设置为false来关闭所需的消息:

# turn the detached message off
git config --global advice.detachedHead false

detachedHead

当您使用git-checkout(1)移动到分离HEAD状态时显示的建议,以指示如何在事后创建本地分支.

advice.*

这些变量控制旨在帮助新用户的各种可选帮助消息.所有建议.*变量默认为true,您可以通过将这些设置为false来告诉Git您不需要帮助:

您可以在建议后设置以下任何内容:

git config --global advice.<...>


pushUpdateRejected
    Set this variable to false if you want to disable 
        pushNonFFCurrent,
        pushNonFFMatching, 
        pushAlreadyExists, 
        pushFetchFirst, and 
        pushNeedsForce simultaneously.

pushNonFFCurrent
    Advice shown when git-push(1) fails due to a non-fast-forward update
    to the current branch.

pushNonFFMatching
    Advice shown when you ran git-push(1) and pushed matching refs
    explicitly (i.e. you used :, or specified a refspec that isn’t your
    current branch) and it resulted in a non-fast-forward error.

pushAlreadyExists
    Shown when git-push(1) rejects an update that does not qualify
    for fast-forwarding (e.g., a tag.)

pushFetchFirst
    Shown when git-push(1) rejects an update that tries to overwrite a
    remote ref that points at an object we do not have.

pushNeedsForce
    Shown when git-push(1) rejects an update that tries to overwrite a
    remote ref that points at an object that is not a commit-ish, or make
    the remote ref point at an object that is not a commit-ish.

statusHints
    Show directions on how to proceed from the current state in the output
    of git-status(1), in the template shown when writing commit messages in
    git-commit(1), and in the help message shown by git-checkout(1) when
    switching branch.

statusUoption
    Advise to consider using the -u option to git-status(1) when the command
    takes more than 2 seconds to enumerate untracked files.

commitBeforeMerge
    Advice shown when git-merge(1) refuses to merge to avoid overwriting
    local changes.

resolveConflict
    Advice shown by various commands when conflicts prevent the operation
    from being performed.

implicitIdentity
    Advice on how to set your identity configuration when your information
    is guessed from the system username and domain name.

detachedHead
    Advice shown when you used git-checkout(1) to move to the detach HEAD
    state, to instruct how to create a local branch after the fact.

amWorkDir
    Advice that shows the location of the patch file when git-am(1) fails
    to apply it.

rmHints
    In case of failure in the output of git-rm(1), show directions on
    how to proceed from the current state.