-
Notifications
You must be signed in to change notification settings - Fork 51
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
g10k not stopping on wrong :commit #91
Comments
chutzimir
added a commit
to chutzimir/g10k
that referenced
this issue
Feb 8, 2018
`git rev-parse --verify` would not throw an error if the input "looks" like a commit id, e.g. it is 40 hexadecimal characters. Therefore, check that `git archive` exited with no errors. Fixes xorpaul#91
Yeah, and |
Hmm, I could also adjust the parameter to check for really existing objects and not accept commit-ish looking parameters. Taken from the
|
Also fixed with 9d8ab0e#diff-b112433c20987b983fa33aa1eac9482dR136 |
xorpaul
added a commit
that referenced
this issue
May 17, 2018
xorpaul
added a commit
that referenced
this issue
May 17, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce:
I was expecting the g10k command to fail.
The text was updated successfully, but these errors were encountered: