We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Tagged releases are not capturing the right version number from CI.
The describe that is used to generate the version numbers doesnt like this section of the checkout action
/usr/bin/git rev-parse refs/tags/v0.2.0-rc1 d5b5a08651c653eaa35cca8ba75c093553058cdf /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules origin +8973e4e52a9f3ae149185e2491a084ef3df14f71:refs/tags/v0.2.0-rc1 From https://github.com/ctc-oss/fapolicy-analyzer t [tag update] 8973e4e52a9f3ae149185e2491a084ef3df14f71 -> v0.2.0-rc1
This can be reproduced locally using the same commands that the checkout action uses. I'm not yet sure why the fetch is structured the way it is.
The text was updated successfully, but these errors were encountered:
https://github.com/ctc-oss/fapolicy-analyzer/runs/2835212833?check_suite_focus=true#step:6:416
Sorry, something went wrong.
The fetch --no-tags appears to be the culprit
fetch --no-tags
https://github.com/actions/checkout/blob/v2.3.4/src/git-command-manager.ts#L173-L175 actions/checkout#258 (review)
Appears that leaving the ref empty on the checkout was causing this...
Fixed with
- uses: actions/checkout@v2 with: ref: ${{ github.ref }} fetch-depth: 0
Successfully merging a pull request may close this issue.
Tagged releases are not capturing the right version number from CI.
The describe that is used to generate the version numbers doesnt like this section of the checkout action
This can be reproduced locally using the same commands that the checkout action uses. I'm not yet sure why the fetch is structured the way it is.
The text was updated successfully, but these errors were encountered: