-
-
Notifications
You must be signed in to change notification settings - Fork 397
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
'fatal: ref HEAD is not a symbolic ref' errors #163
Comments
Hi @mpdude
|
That seems to fix it! Thanks @peter-evans and sorry for not reading the documentation properly. |
would the same be true for a publish event? name: Release Actions on: Looks like I'm running into this |
@ldelossa Replied to your issue here: #522 (comment) |
Tk/ci skeleton There is an error from `git symbolic-ref HEAD` during the build ``` sed "s/BBB/"`git symbolic-ref HEAD | cut -b 12-`"/" verstr.f90 | sed "s/RRR/"`git describe --tags`"/" >> datestamp.f90 10 fatal: ref HEAD is not a symbolic ref ``` This is because the action runs on a merge commit, not a branch, as explained in [this issue](peter-evans/create-pull-request#163). I assume parsing the branch name fails, but since this only runs in the GHA runner, I don't think we should mind too much.
Since recently, this action here fails for me when running on pull requests. Unfortunately, I don't have a public repo right now that shows the issue, but here's an abridged log:
I am suspecting this might have something to do with changes in the
actions/checkout@v2
action made at the end of last year, see here:actions/checkout#23
In particular, this comment says
I don't know enough about
git
internals to fully understand this, but it sounds as if theactions/checkout
action now always leaves us indetached head state
on a SHA instead of being checked out on something that feels like a branch.Not sure if here is the right place to fix this (or if it can be fixed), but I guess
actions/checkout
is such a central thing that they knew what and why they were doing it that way.The text was updated successfully, but these errors were encountered: