Should there be an option for the
pull commands to automatically include all dependencies of the changes to be pushed/pulled?
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..
You’re right actually. I wasn’t clear on what to do there, another option would be to display feedback in the text editor.
Yeah, currently it’s hard to know what dependencies are going to be needed as you’re selecting changes.
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.
Done! When there are missing dependencies, push and pull now complete the list an propose the new list to the user.