-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option for specifying Git revision to compare against #42
Labels
enhancement
New feature or request
Milestone
Comments
akaihola
added a commit
that referenced
this issue
Aug 7, 2020
4 tasks
akaihola
added a commit
that referenced
this issue
Aug 7, 2020
akaihola
added a commit
that referenced
this issue
Aug 7, 2020
akaihola
added a commit
that referenced
this issue
Aug 8, 2020
akaihola
added a commit
that referenced
this issue
Aug 8, 2020
akaihola
added a commit
that referenced
this issue
Aug 8, 2020
akaihola
added a commit
that referenced
this issue
Aug 8, 2020
akaihola
added a commit
that referenced
this issue
Aug 8, 2020
akaihola
added a commit
that referenced
this issue
Aug 8, 2020
akaihola
added a commit
that referenced
this issue
Aug 9, 2020
akaihola
added a commit
that referenced
this issue
Aug 10, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Darker now always compares the working tree against Git
HEAD
to find out which lines were changed. It would be useful to allow comparisons against other revisions as well. One use case is to compare a feature branch to the branching point so formatting and linting fixes can be done before merging.This could be implemented with a
-r
/--revision
command line argument, defaulting toHEAD
, and being used indarker.git.git_get_unmodified_content()
. That function would include the revision when callinggit show <revision>:/<path.py>
.The text was updated successfully, but these errors were encountered: