-
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
Allow fetch-depth to fetch tags within that depth #448
Comments
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? |
joeljeske
referenced
this issue
in bazelbuild/bazel-watcher
Mar 22, 2021
genofire
added a commit
to Kukoon/media-server
that referenced
this issue
May 1, 2021
I'm also seeing this behaviour with /cc @ericsciple |
I forged a pull request that fixes this issue by introducing a |
This was referenced Sep 19, 2021
jaraco
added a commit
to jaraco/pytest-checkdocs
that referenced
this issue
Nov 8, 2021
This was referenced Oct 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
is the command that gets run
https:/bitcoin-s/bitcoin-s/runs/1947728258#step:2:40
The text was updated successfully, but these errors were encountered: