-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
install should install and update according to the .lock #65
Comments
Oh, you actually hit a FIXME: https://github.com/ysbaddaden/shards/blob/464caddde295140ffd085c0894462e25235fc5a5/src/resolvers/git.cr#L54 |
Can you confirm this is fixed? Or do you still have bugs with locked commits? If everything's OK, I'll release v0.5.3 and upload binaries, which would fix #69 |
Mmh, actually the second case still doesn't work, the worktree isn't updated:
|
Exact. Hopefully this is now fixed. |
Well, you broke your testsuite :) |
And I'm getting
|
version: 1.0
shards:
web:
git: file:////home/julien/work/github/shards/test/.repositories/web
commit: Seems like the broken test catched it. The sha1 is missing in the lock file. |
Fixed? Maybe... |
Looks good to me! |
Cool! |
Let's have a project and a library
Let's clone our project to install it somewhere else:
Okay, first bug, lock is still the same, output has claimed to install
1c5d802a
, actually installed is6b0b9e8
.Let's get rid of that
clone
, update the lock to6b0b9e8
and clone and install again.Mkay, we called install, lock stays the same but the worktree is the updated version again. But that's probably the same bug as above. Time to update the lock. Then let's clone our project again and install
Everything good so far. Time to fix something in the library.
And now we got the above bug in reverse, install claimed it installed
94417f5
but the worktree wasn't updated.The text was updated successfully, but these errors were encountered: