Jakob Reschke

Pushing single commits that only touch a single class does seem to work.

In my image under Windows, retrying to push a set of commits that already failed once will most probably fail again. However, we did observe in another image under Mac...

I have recently got a new machine which is quite a lot faster than my notebook. The ConnectionClosed error did not happen once with it, so far. So the problem...

Not sure, I think you would have to inject the slowdown into the WebClient or Socket code. I figured the GitHub guys have better things to do than giving support...

I have not seen this issue for a few months now. There were some changes in Squeak's WebClient, so maybe there was a bug in it that is fixed now....

@Oluwoye Can you provide me with the URL of your repository, so I can have a look at the generated history and what was pushed? And concerning the Connection closed...

I have not seen this at all in the meantime. Closing until someone says it is still broken.

Well, the good news is that there is nothing wrong with the push, but the bad news is that you have run into issue #53. The workaround is to do...

For remote repositories, the lost update problem of writing to the same branch is solved by preventing updates that would remove a commit from the history (you would have to...

If images were mapped to worktrees by the image file path automatically (whenever Squeak accesses the repository), and you manage to corrupt a Squeak image or make it somehow unsusable,...