You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue #84 was about a specific use case and the initial suggestion was a bit of a false start. By the end of the issue discussion I think there was a useful proposal in this comment.
The current use of commit_precocessors just allows a regex replacement to run on matching patterns. I propose a new feature that filters the message through an external command. The commit message would be passed on STDIN and a replacement read back from STDOUT. This would allow all sorts of filtering, format conversion, etc.
I think the remaining questions are things like:
Whether the external command filter should happen before/after/or exclusive of regex replacements. (To my use cases this is a bit of a wash.)
How exit codes should be considered. (I suggest any errors be considered fatal, a different approach might be to skip commits that error, but I suggest a different mechanism such as skipping anything that returns an empty string but a success exit code.)
Whether any useful ENV vars should be set that would enable a filter script to do fancier things like read the commit themselves (e.g. maybe setting the current commit sha in an env var would be useful).
The text was updated successfully, but these errors were encountered:
Issue #84 was about a specific use case and the initial suggestion was a bit of a false start. By the end of the issue discussion I think there was a useful proposal in this comment.
The current use of
commit_precocessors
just allows a regex replacement to run on matching patterns. I propose a new feature that filters the message through an external command. The commit message would be passed on STDIN and a replacement read back from STDOUT. This would allow all sorts of filtering, format conversion, etc.I think the remaining questions are things like:
The text was updated successfully, but these errors were encountered: