We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Similar to the date filter, allow users to specify a commit hash and only return commits after that one.
Examples
gitnstats --commit-filter 316d76d8602a62454c4eb7ad5716e8b49883efcb gitnstats --commit-filter 316d76d gitnstats -c 316d76d
I think the -c and -d options should be mutually exclusive, but I'm not 100% sure.
-c
-d
I also need to carefully consider what to do with branches. Consider the following history.
/----b-----c----\ ---/--a-----d--------\---e
If the user requests commits that occurred after d, should b and c be returned, as they were merged after d? Or should just c be counted?
d
b
c
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Similar to the date filter, allow users to specify a commit hash and only return commits after that one.
Examples
I think the
-c
and-d
options should be mutually exclusive, but I'm not 100% sure.I also need to carefully consider what to do with branches.
Consider the following history.
If the user requests commits that occurred after
d
, shouldb
andc
be returned, as they were merged afterd
?Or should just
c
be counted?The text was updated successfully, but these errors were encountered: