The sound distributed version control system

#67 push/pull: automatically include dependencies

Closed on November 22, 2020
loewenheim on November 15, 2020

Should there be an option for the push and pull commands to automatically include all dependencies of the changes to be pushed/pulled?

pmeunier on November 15, 2020

This is actually the case: pull applies changes recursively, and if you look at line 179 here, push checks dependencies.

loewenheim on November 15, 2020

But doesn’t it only check them in the sense that it throws an error if a dependency is missing? I was thinking of automatically pushing them along with the explicitly given ones..

pmeunier on November 15, 2020

You’re right actually. I wasn’t clear on what to do there, another option would be to display feedback in the text editor.

loewenheim on November 15, 2020

Yeah, currently it’s hard to know what dependencies are going to be needed as you’re selecting changes.

cole-h added a change on November 16, 2020
OAXTXEAFX6YLO2XX6L4VMCVW4YZSIXWL6QOZKQCDSL7M44QNX66AC
main
cole-h on November 16, 2020

I’ve pushed a change that will display the dependencies of a particular change in the push/pull edit buffer. I only went for the direct dependencies rather than every dependency just for ease of implementation. There may be a better / more robust solution, but this is what I came up with after hacking away for a few minutes.

pmeunier added a change on November 22, 2020
M5FK3ABTKBDG6HHW32G7UKRJEJQKD2U7BPXNZ3HVHBKULWVV6CTQC
main
pmeunier on November 22, 2020

Done! When there are missing dependencies, push and pull now complete the list an propose the new list to the user.

pmeunier closed this discussion on November 22, 2020