-
-
Notifications
You must be signed in to change notification settings - Fork 199
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
Gitlab CI, git-cliff is working on v0.4.0, git repo is set, config file is here but no changelog ... #22
Comments
Are you sure you have the full commit history in the current path that you're trying to run git-cliff? I had a similar issue with GitHub actions where actions/checkout was only fetching the latest commit thus makes the git-cliff create an empty changelog. For the record, here is how you solve it: - uses: actions/checkout@v2
with:
fetch-depth: 0 Maybe GitLab has something similar? |
I see you created #24, does that mean you have solved this issue? |
I actually tried the first workflow you posted and it worked for me. Are you using the default |
Yep i know it worked I use it on another repository without any issue but on this one. Yes i am using the default cliff.toml file. On my machine everything is working fine but on the CI it is not working :/ |
Is this a public repository? I want to take a look. |
This is a private repo 😥 |
Hi, try to set these variables in the job to make a full clone: variables:
GIT_STRATEGY: clone # clone entire repo instead of reusing workspace
GIT_DEPTH: 0 # avoid shallow clone to give cliff all the info it needs] (Similar to Also I'm using |
It works !!! That's so good ! I am wondering why my example is running then :/ |
I have updated the PR accordingly |
Describe the bug
I set the Gitlab CI with the following stage
here is the result on Gitlab CI
here on local
I don't understand why it is not working.
I try to reproduce the error but impossible on a new repo :/
If you have any idea where it can come from
System (please complete the following information):
The text was updated successfully, but these errors were encountered: