Nerglish

Ever forget which branch you were working on? Here's a little snippet to list the most recent git branches by commit date.

Add this to your ~/.gitconfig*

[alias] recent-branches = !git for-each-ref --sort='-committerdate' --format='%(committerdate)%09%(objectname:short)%09%(refname)' refs/heads | sed -e 's,refs/heads/,,' | head

Usage:

git recent-branches -n 5 Wed Oct 30 14:59:58 2019 -0700 fd658fd master Wed Oct 30 14:57:05 2019 -0700 8a4c5a4 feature/docker-unit-tests Wed Oct 30 13:19:45 2019 -0700 783ae60 feature/increase-num-threads Tue Oct 29 16:06:40 2019 -0700 ac3c9d2 bugfix/hash-collisions Tue Oct 29 15:33:51 2019 -0700 f2c1ab1 feature/wip

Command line:

Can also just commands on the command line

git for-each-ref --sort='-committerdate' --format='%(committerdate)%09%(objectname:short)%09%(refname)' refs/heads | sed -e 's,refs/heads/,,' | head

In case you're wondering the %09 is a tab character in the git for-each-ref formatting.

References:

https://davidwalsh.name/sort-git-branches

I like how Prime Directive statement sets up a safe environment for discussing and learning from potentially uncomfortable things like failures or areas of improvement.

If you've edited the configuration file in /etc/init/*.conf for a running Upstart service, calling restart will not put your changes into effect. You need to run stop and start to reload configuration

# put updated configuration into effect stop myservice && start myservice

http://upstart.ubuntu.com/cookbook/#restart

You can get ec2 instance metadata including instance id and ami id from within an ec2 host.