If you can see this, your browser sucks

Github game-off 2012

You're working on the coolest project ever. Unfortunately, so are your friends! With the fierce competition, you want to merge in as much of their code as possible, without letting them get hold of yours.

The red line is your revision graph. Collide with another revision graph, and you'll merge in, giving your friends all your awesome code! Try to force them to give their code to you by cutting them off. Points are awarded for each commit integrated into the graph.

In a fix? Branch your repository to split your revision graph in two!


Your revision graph is directed with a set of arrow keys. When you have multiple branches, you'll need multiple sets at the same time! The four available sets of controls are show below

w a s d e
i j k l o
8 4 5 6 7

For each set of controls, the directional keys control the direction, and the fork key, in orange, causes the branch to split in two. Your initial branch will start off with wasde as its controls.

The HEAD of each branch will be labeled with its controls, so you can remind yourself which set of keys controls which branch.

Easy Hard