Closed
Description
I'm using github actions to push docker images to dockerhub and require tags to make sure my artifacts version is correct.
I'm using fetch-depth: 500
to avoid really long fetch times with my repo (yes, I know this is a problem on it's own).
I would expected the default behavior of the action is to checkout tags within that 500 depth limit, not use --no-tags
/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=500 origin +cd1e2e1b5d307b7f4a2c6e49113da14cfc7b1c36:refs/remotes/origin/master
is the command that gets run
https://github.com/bitcoin-s/bitcoin-s/runs/1947728258#step:2:40
Metadata
Metadata
Assignees
Labels
No labels
Activity
freddyrios commentedon Mar 9, 2021
Got hit by this and I don't get why no-tags is used in the first place.
Local testing shows:
Can't see the downside, just some extra metadata being pulled?
Add more debugging to the "create NPM package" step
ci: checkout workaround
hairyhenderson commentedon Jul 12, 2021
I'm also seeing this behaviour with
fetch-depth: 0
, which contradicts what the docs say... Maybe something broke since #258?/cc @ericsciple
RobertWieczoreck commentedon Sep 19, 2021
I forged a pull request that fixes this issue by introducing a
fetch-tags
option: #579Reviews and thumbs-ups are very welcome :)
Update comment to reference actions/checkout#448 as the upstream issue.