Distilled Hype — by Kahlil Lechelt

DESCRIPTIVE 2: I Can Parachute into Anybody's Project with Brandon Hays →

Brandon Hays talks to Kahlil about Frontside, why Frameworks are awesome and refactoring legacy jQuery code into EmberJS components.

I was a little sleep-deprived when recording this but it was great fun and Brandon is a tremendous guest.

DESCRIPTIVE 1: A Little Bit of Everything with Philip Roberts →

As a podcast fan with ambitions of being a podcaster I have been thinking about launching my podcast for a long time.
I finally decided on a format and started production.

DESCRIPTIVE is an interview podcast with people from the JavaScript and web development world.

I am happy to announce the first episode with my very esteemed guest Philip Roberts who is a JSConf.eu speaker and works for &yet.

We talked about his way into development and JavaScript, as well as his JSConf.eu talk about the event loop, &yet and AmpersandJS.

JSJabber 128: Famo.us with Steve Newcomb →

Steve Newcomb explains what the deal is with Famo.us.
If you are building user interfaces you have to listen to this.

Shoptalkshow with @bastianallgeier →

Bastian talks to Chris and Dave about Kirby, Kirby's business model and Kirby v2. Highly recommended.

Checking Out Remote Git Branches

I just joined a project that has a lot of remote Git branches. In order to be able to work I had to check out just couple of them. I had no idea how to do it.

First, because I was to lazy to google for it I just made branches from master and named them after the remote branch and did a git pull. Git then gets all "Yo dawg, where do you want me pull from? Here is how you can set up this branch to track a remote branch so I know where to pull from". Git is very friendly like that. So I set up the local branch to track the right remote branch and pulled from there. Whee that worked! Kinda. Mostly.

It can also create unnecessary conflicts depending from which branch you branched off.

So since this solution is neither simple nor efficient I finally scoured the net for that way simpler solution that had to exist and of course it does. I found what I needed on gitready:

git checkout -t <remote>/<tracked branch>

This creates and checks out a branch locally that tracks the specified remote branch, it is also named identically to that remote branch. So if I wanted to checkout a branch called "dev" from the remote repo named "origin" it would look like this:

git checkout -t origin/dev

Short and sweet <3

Of course there is a long version of this command as well. It lets you set the local branch name explicitly.

git checkout --track -b <local branch> <remote>/<tracked branch>

Using the example above it would translate to:

git checkout --track -b dev origin/dev

Definitly a little command one should have handy.