Open sebastianbergmann opened 4 years ago
I think this makes a lot of sense: when we designed this package, a lot of focus was put into trying to keep the current repo isolated from the rest, but the --to
could indeed be the current state of the project, rather than a clean copy.
Not going to be able to drag this into 6.0
- removing milestone for now.
It is confusing, at least to me, that this tool does not compare to the current state of the working copy and ignores uncommitted changes.
I think it would make sense to use the current state of the working copy instead of the latest commit when
--to
is not used.