-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Can't checkout to head after calculating diff #1186
Comments
When I do:
This is the output:
Why? Can you reproduce this? |
No I can't reproduce, I get empty output. (orhun ζ ~) cdtmp
(orhun ζ /tmp/tmp.KD9evKrYTF) git clone git@github.com:orhun/rattler.git
cd rattler
Cloning into 'rattler'...
remote: Enumerating objects: 6956, done.
remote: Counting objects: 100% (1294/1294), done.
remote: Compressing objects: 100% (383/383), done.
remote: Total 6956 (delta 968), reused 1116 (delta 904), pack-reused 5662
Receiving objects: 100% (6956/6956), 18.03 MiB | 2.92 MiB/s, done.
Resolving deltas: 100% (3924/3924), done.
Updating files: 100% (483/483), done.
Filtering content: 100% (25/25), 330.02 MiB | 2.92 MiB/s, done.
(orhun ζ /tmp/tmp.KD9evKrYTF/rattler) git status --porcelain
# nothing |
ooooh that's why it doesn't work for me:
I will install git-lfs 👍 EDIT: I managed to reproduce the issue locally with |
The error is in the rattler-bin package. It has something to do with git-lfs and the If you don't plan to publish rattler-bin you can add the |
I'm closing this. Let me know if you still need help :) |
Unfortunately for me this still happens. Even if I added |
What's this test file and why it's created? |
Its a file we use in the tests that is pretty big. Therefor it is stored in lfs. I could potentially store it not in lfs but the history would still include the lfs file. |
Bug description
I am trying to integrate
release-plz
into therattler
project. You can see my configuration from this commit.However, I'm getting the following CI error during testing:
Does that mean a file is changing during the calculation of the next release? I think this shouldn't happen.
To Reproduce
Steps to reproduce the behavior:
rattler
release-plz
as mentioned before.Expected behavior
Successful CI build.
Environment
MarcoIeni/release-plz-action@v0.5
Additional context
See https://github.com/orhun/rattler/actions/runs/7408098693/job/20155636867
The text was updated successfully, but these errors were encountered: