$ git commit
.git/hooks/prepare-commit-msg: line 43: conditional binary operator expected
.git/hooks/prepare-commit-msg: line 43: syntax error near `=~'
.git/hooks/prepare-commit-msg: line 43: `  if [[ "${IGNORED[*]}" =~ "${filename}" || "${IGNORED[*]}" =~ "${extension}" ]]; then'

$ cd ../commit-comments/
$ git log | head -n 1
commit a916600e8cc2b0cb0f6da2533d616da3ddca5f68

$ /bin/bash --ver

I would really appreciate seeing this limitation documented a little further.

Specifically I would like to understand the issue with merge commits and know if there is a migration path from a codebase with a long history of these to one which would be ready to use fbshipit.

Running these commands

git clone https://github.com/paramiko/paramiko.git
cd paramiko
git checkout -b my2.2.3 2.2.3
git tag to-backport 56c96a65
git deps -r -e my2.2.3

I get

Fatal: -L invalid line number: 0
Traceback (most recent call last):
  File "/usr/bin/git-deps", line 10, in <module>
    sys.exit(run())
  File "/usr/lib/python3.6/site-packages/git_deps/cli.py

When releasing the last mochify version I forgot to add a new contributor to package.json and had to do that manually afterwards.

Should changes do that (which probably wouldn't be too hard to do as everything is already there)? Or should its scope stay limited to the CHANGELOG?

Rather than requiring regex to delete comments, it would be great if this would automatically check if the comment exists, and if so, do not add a further comment.

For example, when setting up a PR review environment, we don't want it to constantly post the URL to the PR. We only need it done once.

From @sfabrizio on September 12, 2016 17:24

We have some new staff that we are not showing in the demo git yet.

Copied from original issue: labs-js/turbo-commit#36