Signed-off-by: James Couball <jcouball@yahoo.com>

As described by git-rev-parse:
  Many Git porcelainish commands take mixture of flags (i.e. parameters
  that begin with a dash -) and parameters meant for the underlying git
  rev-list command they use internally and flags and parameters for the
  other commands they use downstream of git rev-list. This command is
  used to distinguish between them.

Using the `--` to separate revisions from paths is at the core of git.
I do not think this behavior will ever change.

The message without the extra parameters:
  fatal: ambiguous argument 'v3': unknown revision or path not in the
  working tree.
  Use '--' to separate paths from revisions, like this:
  'git <command> [<revision>...] -- [<file>...]'

The message with new parameters:
  fatal: bad revision 'NOTFOUND'

I think it's way more descriptive.

Signed-off-by: James Couball <jcouball@yahoo.com>

- Add steps to bin/setup to install husky and the commitlint npm packages
- Configure husky to run commitlint via the commit-msg hook
- Add commitlint configuration based on my specific preferences
- Add npm specific files (node_modules/, package-lock.json) to .gitignore

- Add a GitHub Actions workflow to enforce conventional commits
- Add commitlint configuration based on my specific preferences

Use googleapis/release-please-action and rubygems/release-gem actions
to automate releasing and publishing new gem versions to rubygems.

…'main'

…ushed to master