incorrect change_type
#1561
|
shouldn't this be a |
Answered by
Byron
Mar 10, 2023
Replies: 1 comment
|
Which way around is right has always been troublesome for me as In Changing anything in GitPython would be a breaking change and thus can't be done, but either one can add new names to make direction clear, or code has to be adjusted to be |
0 replies
Answer selected by
Byron
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Which way around is right has always been troublesome for me as
diffdoesn't convey the direction into which the diff should go, at least not without prior training.In
gitoxide, I usetree.(get_)changes_to_obtain(other_tree)which makes clear what needs to be done to turntreeintoother_tree. Without the notion of direction, things can look reversed pretty quickly.Changing anything in GitPython would be a breaking change and thus can't be done, but either one can add new names to make direction clear, or code has to be adjusted to be
target.diff(index).