GitHub / jryio/commit-comments issues and pull requests
#13 - have GNU grep 2.20, but get "grep: Invalid range end"
Issue -
State: open - Opened by franzinc almost 7 years ago
#12 - Any plans to support Windows?
Issue -
State: open - Opened by bendtherules about 8 years ago
#11 - Use `git grep` instead of external tools
Issue -
State: open - Opened by hauleth over 8 years ago
#10 - Multiline commit messages
Issue -
State: open - Opened by darvid over 9 years ago
- 1 comment
Labels: enhancement
#9 - Overzealous commits when using `git add --patch`
Issue -
State: closed - Opened by bogwonch over 9 years ago
- 2 comments
Labels: bug, enhancement, help wanted
#8 - Implement file name and line number formatting
Pull Request -
State: closed - Opened by jryio over 9 years ago
Labels: enhancement
#7 - Portability for pcregrep in post-commit hook
Pull Request -
State: closed - Opened by jryio over 9 years ago
Labels: portability
#6 - pcregrep not found in post-commit
Issue -
State: closed - Opened by fbartels over 9 years ago
- 6 comments
Labels: portability
#5 - Take advantage of more accurate comment to code mapping?
Issue -
State: closed - Opened by amichail over 9 years ago
- 6 comments
#4 - Fix GNU grep compatibility.
Pull Request -
State: closed - Opened by jryio over 9 years ago
#3 - Leave repository in clean state after commit
Pull Request -
State: open - Opened by hauleth over 9 years ago
- 2 comments
Labels: enhancement, help wanted
#2 - OSX: sed -r isn't available
Issue -
State: closed - Opened by rstacruz over 9 years ago
- 3 comments
Labels: portability
#1 - Files that aren't in the commit are searched for commit comments
Issue -
State: open - Opened by SonOfLilit over 9 years ago
- 9 comments
Labels: bug, portability