Assorted helpers for working with git.

Add the path to this installation directory and update $XDG_CONFIG_HOME in your .bashrc file (or .bash_profile for OS X) as follows:

# Load git commands and aliases from git-more  <https://github.com/Erik-Codeblind/git-more>
export PATH="$PATH:$HOME/Development/git-more"
export XDG_CONFIG_HOME="$HOME/Development/git-more"

Source your current terminal or open a new one for changes to take effect.

This includes a custom git config file with numerous aliases. Have a look therein for more information. Your global .gitconfig can be used to override and augment any rules defined here.

git branchify Unformatted Branch Title String
git cob Unformatted Branch Title String

This command allows you to create new branches with checkout -b, while automatically formatting the branch name to lower kebab-case. It is useful for managing long branch names, especially when cutting and pasting from Jira ticket titles.

$ git branchify Branchify Makes It Easy To Cut-and-Paste Branch Names
Switched to a new branch 'branchify-makes-it-easy-to-cut-and-paste-branch-names'

Aliases exist for prepending common prefixes.

$ git bug Fixing This Bug
Switched to a new branch 'bug/fixing-this-bug'

$ git feature My New Feature
Switched to a new branch 'feature/my-new-feature'

$ git hotfix Oh NO A Hotfix
Switched to a new branch 'hotfix/oh-no-a-hotfix'

$ git spike Giving this a try
Switched to a new branch 'spike/giving-this-a-try'

git bulk-delete [-D force delete un-merged branches]
git del

Loops over branches in a repo and provides the user with an opportunity to delete the currently listed branch.

• Enter "y" or "yes" to run git branch -d on the listed branch.
• Entering "q" or "quit" will exit the program.
• Empty return skips to the next item, leaving current item intact.

Calling git-bulk-delete with the force delete flag -D allow for the removal of selected un-merged branches. No warning is given as to the merge status of a given branch.

By default the "master" and "develop" branches will be ignored, so you can't accidentally delete them.

git find-branch 'grep friendly search pattern'
git fbr 'grep friendly search pattern'

Runs a grep expression against the branches in your repo.

• If a solitary match is found, it will check out that branch immediately.
• When multiple matches are located, they will be listed as index and user may select which one to checkout.
• An empty return quits without changing from the current branch.

Our working directory has three branches.

$ git branch
  exampleA
* master
  example1

Search for branches with "example" in their name and checkout item 1, example1.

git find-branch example
Found the following...
0: exampleA
1: example1
Which branch should I checkout? 1
Switched to branch 'example1'

Search for branch "master". There is only one match, so it is immediately checked out.

$ git find-branch master
M       README.md
Switched to branch 'master'

git pull-request-checkout PR#
git copr PR#
git prco PR#

Fetches the HEAD of a pull request by the PR ID and checks it out as a new branch. If the optional second argument is passed, it will be used to name the new branch, otherwise the branch will be named with the PR ID.

Naming the branch.

git copr 976 my_branch
[...snip...]
 * [new ref]         refs/pull/976/head -> my_branch
Switched to branch 'my_branch'

Defaulting to pull request ID for branch name.

git copr 977
[...snip...]
 * [new ref]         refs/pull/977/head -> 977
Switched to branch '977'

No pull request found throws expected error.

git copr 978
fatal: Couldn't find remote ref pull/978/head

git push-this
git put

Push the current branch to the origin repo. The master and develop branches are protected. Pushing to these branches is not allowed.

git put
Total 0 (delta 0), reused 0 (delta 0)
To [email protected]:Erik-Codeblind/git-more.git
 * [new branch]      my_branch -> my_branch