Morten Christensen

I was just to add this one myself. I'll give this one a big thumbs up and add a scenario below. During development you might do more ad-hoc tasks like...

Cool ... I haven't looked at this repo in a long time, but I know people still find it and use the example, so this PR is most definitely welcome....

LOL ... Birthday greeting as a pull request :sparkles:

Yeah, I believe that is because of a rogue Console.WriteLine in the Core. Which version of umbraco did you try this with?

Okay, had a chance to look into the codebase. I see both `Push` and `Fetch` on the `Network` class uses `RemoteCallbacks` but while `Fetch` passes the `FetchOptions` to the ctor...

Are there any tests that cover the progress callback during Fetch in libgit2, which I can look at to investigate and test for possible differences? **Update**: Found this [example](https://github.com/libgit2/libgit2/blob/2d9291943c253e9e1520f87b13abb1e81cffdb29/examples/network/fetch.c) which...

This must be the pull request you referred to right @carlosmn https://github.com/libgit2/libgit2/pull/1410 I'll try to digg through this.

@jamill I see you worked on Push progress reporting in 981f43909ca79b3b9e5c5a34590d76ecd5c82e3f but as far as I can tell it only shows errors (`OnPushStatusError`) and not other responses from the remote...

I just tested this and the `OnProgress` handler now works as expected when I add it to the `PushOptions`. Thanks for the heads up @uluhonolulu I'd be happy to submit...

I wish I had submitted a pull request for this a long time ago as now I really need it 😅 Anyway, if anyone else is still looking for this...