-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suppress hint: You are in 'detached HEAD' state. #494
Comments
I disagree. I caught a bug in our GitHub Actions workflow only because I noticed this log. The log offers clarity about what is going on (which is the point of logs). If people misinterpret them, that's on them. |
jeffwidman
added a commit
to jeffwidman/checkout
that referenced
this issue
Oct 24, 2022
Checking out certain `ref` values will result in a warning about a detached `HEAD`: ``` You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by switching back to a branch. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -c with the switch command. Example: git switch -c <new-branch-name> Or undo this operation with: git switch - Turn off this advice by setting config variable advice.detachedHead to false ``` However, this warning isn't useful in a CI environment... so suppress it. I realize on the original bug report that one user mentioned this warning highlighted a bug in his actions flow, but I consider that a super rare / happy accident. 99% of use cases will be _intentionally_ checking out a specific ref where the detached head state is inevitable, so the warning is pure noise. Passing the config this way sets it _only_ for this command. Note that it must be set [_before_ calling `checkout`](https://stackoverflow.com/a/72588008/770425). Resolve: actions#494
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Downstream consumers of actions shouldn't see noise that git is checking out a detached head. When
actions/checkout
is used, it will be given something specific to check out, and if that results in a detached head, that's clearly intentional...The text was updated successfully, but these errors were encountered: