-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
fetch-tags is not working according to the docs with v4 #1781
Comments
I'm getting this too. I don't want to set fetch depth to 0. e: Looks like this still breaks if I use |
We should not be required to add this, but fetch-tags: true seems broken. See actions/checkout#1781 for a second opinion, and possible resolution.
We should not be required to add this, but fetch-tags: true seems broken. See actions/checkout#1781 for a second opinion, and possible resolution.
We should not be required to add this, but fetch-tags: true seems broken. See actions/checkout#1781 for a second opinion, and possible resolution.
checkout@v4 fetch-tags: true does not seem to work as expected [1]. Version matrix ends up missing the tag for stable: matrix={"include":[{"ref":"master","name":"dev"},{"ref":"","name":"stable"}]} Work around this by reverting back to running git fetch --tags manually. [1] actions/checkout#1781
Still an issue. |
The issue looks like this for us: We are running 4.1.7 and use
We use |
Also not working for me. I have
EDIT: You can see that they are not adding |
You need to create a fork of the repo first and then make a PR towards the original repo. |
Hello, hope you're good. I'm running some experiments in order to build a custom action that demands the tags from the repo. I noticed that it was possible, in theory, just using the
fetch-tags: true
, but it does not work. I can only get the tags if I use thefetch-depth: 0
.Example workflow:
The last command (
git tag --sort -creatordate
) shows nothing in this case.But, if I use the
fetch-depth: 0
, it lists correctly the tags from the repository.The text was updated successfully, but these errors were encountered: