An already sucessfully pushed commit keeps showing it needs to be pushed
I have a situation where, on my one PC, using Sourcetree an already successfully pushed commit continuously keeps displaying a "3", wanting to push the commit which is already visible on the Git web interface. No errors were shown, and every time I push, it seems to be happy for a while, and then the "3" appears again, without actually making any changes.
I think however the error is on the server side, because, on my other PC, also using Sourcetree, when I fetch, the commit appears, but as soon as I want to pull, it simply disappears and I remain on the commit I was last. This happens even if I switch to another branch and try to update the branch in question. Fetching fetches it, but trying to update it to the latest commit, the "fetched commit" simply disappears and that branch remains on the commit it was before.
Any ideas how I can fix this?
So it turns out somehow capitalization got mixed up. Forcing a push to testing instead of Testing fixed it. My local repo from where I made the push is still Testing now, but it pushes to testing on the remote. The other machine keeps pulling from testing as it has and now also has the complete commit flow.
What is really strange is that fetching it on the other machine seems to discard capitalization differences, but once I pull it, it gets picky. Well, that and, I have no idea how this happened.