-
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
bin: allow file:/// urls to files containing commit messages #11
base: main
Are you sure you want to change the base?
Conversation
|
Add instructions and a hook to call core-validate-commit from git commits. Depends on nodejs#11 Known issues: - leaves ${TMPF} around (temporary file) - probably will reject `fixup:` type commit logs - may be too strict if someone is just doing a simple 'work in progress' kind of local branch Larger improvement: - fold the entire hook script into a mode, and/or an alternate script entrypoint into core-validate-commit. This would drop requirements on sh, sed, grep… Fixes: nodejs#12
Add instructions and a hook to call core-validate-commit from git commits. Depends on nodejs#11 Known issues: - leaves ${TMPF} around (temporary file) - probably will reject `fixup:` type commit logs - may be too strict if someone is just doing a simple 'work in progress' kind of local branch Larger improvement: - fold the entire hook script into a mode, and/or an alternate script entrypoint into core-validate-commit. This would drop requirements on sh, sed, grep… Fixes: nodejs#12
Would it be possible to just allow a filepath, rather than a |
0e79acf
to
658c478
Compare
@not-an-aardvark right now the implementation is that it checks whether it's a valid URL, otherwise assumes it's a sha. I think that makes sense, however, I wasn't sure what the best parameter option would be. I think a related question here is about the format of the input. right now it needs to be equivalent to The current use cases (sha, url) are the higher runner cases for command line usage. Probably this should be handled by just two additional paramteres:
expecting ( |
It may make sense to just make the three different types of inputs (sha, url, file) require a different flag for each one. It would definitely make it less ambiguous. |
add the usage model of
core-validate-commit file:///somefile…
The file needs to approximate the output of
git show --quiet --format=medium ${sha}
Semver: minor