Extend git commands

[charlesreffett]

This will help with the steps defined in our team's project release guide, I believe Iceman also uses a similar process. The goal is to reduce the manual steps needed to make a release.

This PR includes scripts for creating a bin directory in the user's home directory and adding it to the $PATH if it doesn't exist, as well as a script to symlink git- scripts to the bin dir.

The two git scripts extend the git command to add tickets and make-release. The former gets the new tickets from the first branch that are not in the second branch. The make-release will create a new branch and prepend the ticket information in the CHANGELOG.md.

[iBotPeaches]

This looks sweet. Will test it out on some projects.

[erik-perri]

I wonder if we should move git-make-release and git-tickets into the bin folder like hop. We encouraged people to put the bin folder of this project into their path when using hop in the hope it would make things easy to update if bugs were found or new commands were added. It seems like we could get the same benefit by moving these there and just having one path for setting it up.

[charlesreffett]

I wonder if we should move git-make-release and git-tickets into the bin folder like hop. We encouraged people to put the bin folder of this project into their path when using hop in the hope it would make things easy to update if bugs were found or new commands were added. It seems like we could get the same benefit by moving these there and just having one path for setting it up.

Sure, I had a similar thought and if that's something that's already handled in setting up this repo that makes it infinitely easier :)

[charlesreffett]

I wonder if we should move git-make-release and git-tickets into the bin folder like hop. We encouraged people to put the bin folder of this project into their path when using hop in the hope it would make things easy to update if bugs were found or new commands were added. It seems like we could get the same benefit by moving these there and just having one path for setting it up.

Moved the scripts into the project's bin dir, adding that to the path should work

[charlesreffett]

I wouldn't mind this grabbing the ticket summary/title from Jira if anyone has an idea of how we could do that

Discussed in our team meet, if projects squash merged it would put the PR title at the top, we could use that as the default value for the ticket description in the changelog

[iBotPeaches]

Guess my readme changes in Mailpit PR had some negative downsides here

[jyann]

Could maybe link to the hop README.md under docs