-
Notifications
You must be signed in to change notification settings - Fork 534
Pull after Fetch does not update HEAD #198
Comments
@skyflyer Thank you for the report. We'll look into this. With respect to the errors when there is no update, that is the current behavior. |
Thanks for the heads up on that error, that's very useful. |
@smola, I started getting another error from I'm calling it like this: I'm testing this with a master branch (commit Note that I am getting this error only when there are no updates; if there are updates in the repo, all is fine. Even if changes are on some branch. |
Maximo, sure. I'll create another issue in an hour or so. |
Created #208 to track no upload pack error. |
When running
Pull
orFetch
on a FileSystemRepository, they both return an error when there is nothing new to fetch. (should this be a separate issue?)Also, when doing
Fetch
to update repository and thenPull
, I would expect to update my references, but theHEAD
does not get updated.In other words, I see that
Pull
is also performing aFetch
operation, butFetch
is not updating my head. And it is strange thatFetch
andPull
return errors when nothing is to be pulled/fetched.Steps to reproduce:
3897b83b17306309fa8bb570c0404e1403d503bf
)git
tool, push a new commit to the repoFetch
followed byPull
If I don't perform a fetch, the head gets updated to the latest commit. I am calling
Fetch
andPull
methods on a*Repository
instance.After playing with it for some time, I managed to get it into a state, where it would not update the HEAD ref anymore:
2017/01/03 15:37:57 unknown channel ACK a0b3bee218aefd7f10ea45b12efd169edd128cab
Now, even though I perform just a
Pull
operation, the HEAD stays at some earlier commit. If I list the commits, I don't see all of them (the newer ones are missing). Note that the current HEAD is at the value in the error above (a0b3bee218aefd7f10ea45b12efd169edd128cab
).I was testing this on a
master
branch.The text was updated successfully, but these errors were encountered: