-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Why HEAD~1 ? #460
Comments
Hi, thank you! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
if current |
Hi,
I wholeheartedly agree on it being unrealistic to start addressing all existing issues, but rather prevent any new ones.
To that end, why
--new-from-rev=HEAD~1
? That would just show diffs introduced in the last commit only, no?Many PR's are many more commits.
How about instead
--new-from-rev=$(git merge-base master HEAD)
? Or if the PR branch is always properly based on master, could just usemaster
?The text was updated successfully, but these errors were encountered: