You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
Spent quite a bit of time tracking this down with CircleCI. We started getting mysterious build failures with a warning like this when attempting to check out:
warning: refname 'HEAD' is ambiguous.
fatal: Ambiguous object name: 'HEAD'.
Exited with code 128
It turns out we had an earlier build that one of our devs triggered using the circleci-cli with HEADas the branch argument passed to the trigger command. This did not get interpolated to the actual HEAD ref, and instead created a branch in CircleCI with this name. This build failed with the same ambiguous object error, but the result of this build got cached which made downstream builds also fail because they still had the local branch with this name.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Spent quite a bit of time tracking this down with CircleCI. We started getting mysterious build failures with a warning like this when attempting to check out:
It turns out we had an earlier build that one of our devs triggered using the circleci-cli with
HEAD
as the branch argument passed to thetrigger
command. This did not get interpolated to the actual HEAD ref, and instead created a branch in CircleCI with this name. This build failed with the same ambiguous object error, but the result of this build got cached which made downstream builds also fail because they still had the local branch with this name.The text was updated successfully, but these errors were encountered: