I think a sensible way for the changes argument to work is like this: if any of the changes can’t be identified, we return an error with all the invalid changes and do nothing else. If all of them are valid, exactly those changes that have been supplied and that the remote doesn’t have will be pushed.

Sorry, I’ve had to reboot this repository again, since some of the changes it was recording were bad. This is the result of the recent change in the change format. Would you mind recording these changes again, with pijul 1.0.0-alpha.3 (published on crates.io now).

Finally done! Thanks a million for your patience and your change.

My pleasure. I greatly enjoy contributing to this project.

Sorry, I forgot a change to main.rs before. I pushed it just now.

It appears that I can’t pull your change to my local repo because of the various This change could not be retrieved at the moment changes above (maybe?). Could you please remove them from the discussion with the button?

(Of course, I could make the change manually, but this will also make it easier for @pmeunier to apply it :P)

Sorry for this confusion, it’s fixed now. @lowenheim, it seems that you’re not running cargo fmt before recording, I’m adding a part in the README on how to do this.