0cjs

#!/usr/bin/env bash

# If no commits specified, we default to HEAD@{u}..HEAD. However if HEAD is uptodate,
# then `rev-parse` returns nothing. In that case we fallback to HEAD^..HEAD.
# XXX: This breaks if `some-other-brach@{u}..some-other-brach` is specified.
# adding a `--boundary` should have solved this issue, but there seems to be
# a bug in `git rev-parse` and `git rev-list`.
parsed_revs=($(git rev-parse --revs-only "$@" --default HEAD@{u}..HEAD))
[ ${#parsed_revs[@]} = 0 ] && parsed_revs=(HEAD ^HEAD^)

0cjs

Hello there! This is a sample post for gist.io, a super-lightweight writing soapbox for hackers.

Now look up. Further. Above the post title. See that grey text with the gist ID?

Now back to me. That grey text is a link! Open that sucker in a new tab to see the source for this post. Also, I'm on a horse.

This is a major heading

If you peek at it with a web inspector, you'll see that it is a second-level heading. You can use first level headings, but they'll look just like the second level ones, and the gods of the HTML5 outlining algorithm will frown upon you.