Git workflow and my new love of Git alias
Tags: git, macos
Published: 2018-07-24 15:56:08

---
title: Git workflow and my new love of Git alias
published: true
tags: Git,MacOS
canonical_url: http://christine-seeman.com/2018/07/git-workflow-and-my-new-love-of-git-alias/
---

For good or bad, my current Git workflow does not include merges, but rebasing.

![](http://christine-seeman.com/wp-content/uploads/2018/07/Screen-Shot-2018-07-24-at-9.04.01-AM-1024x724.png)

It keeps the history cleaner, works with the established workflow (pretty standard GitHub flow) just no merge commits.  I was trying to find a nice graph of the master branch, but coming from a GitLab background it isn’t hard to find this information in the GitLab repo, but I don’t think GitHub really has this history feature. Anyone know the best way figuring out the history on GitHub?

We really enforce making sure to have meaningful commits, and commit messages. When you are working on your local branch, feel free to commit away, but an [interactive rebase](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History) is needed before requesting your pull request. After you have done a couple of these rebases, there really isn’t anything to be afraid of. I hadn’t done one, and let me tell you, my first pull request was pretty painful. I think getting through the review process on that, and getting my commit history clean took just as long as coding my feature \>\_\<. Now me, rebases, and amends are friends.  I haven’t had a chance to use [fixup commits](https://fle.github.io/git-tip-keep-your-branch-clean-with-fixup-and-autosquash.html) yet, but they are something on my raider to try out soon!

I enjoy using Git bash for my source repository needs.  Even with my more advanced workflow at my company, for me it has the most flexibility.  I have given [Sourcetree](https://confluence.atlassian.com/get-started-with-sourcetree/install-sourcetree-847359094.html) (works better with BitBucket then GitHub) and [Git Kracken](https://www.gitkraken.com/) a try before, and it is nice to have visuals when you need to deal with complex conflict situations, but I keep on going back to my trusty Git Bash.  I never used to be a command line person, just in certain situations, but now especially since I have switched over to Ruby and Rails I have at least 3-4 terminals open at anyone time. I even exited Vim yesterday without having to look it up! I feel that should be some sort of milestone.

![](http://christine-seeman.com/wp-content/uploads/2018/07/Da2x8hMX0AY6ne_-300x260.jpg)

 

 

 

 

 

 

Also I have been making use of GIT CLI alias, also installed multiple scripts to run in the terminal ([terminal parrot](https://github.com/jmhobbs/terminal-parrot) I’m looking at you!).  Some of these help me with my job more then others :). If you don’t have a git alias, get yourself one stat. You just need to add lines to `~/.gitconfig`

```
[alias]
    st = status
    ci = commit -v
```

Some of my personal favorites right now are:

st = status  
co = checkout  
dm = diff –patience master  
prb = pull –rebase  
pu = pull –rebase origin master  
pf = push –force-with-lease  
po = push origin master

What’s in your Git alias? And also how awesome is Command+Option+Shift+V on MacOS? That was the key to my problem with copy and pasting text and not keeping the old formatting!