GitHub Cheat Sheet

As mentioned, these are cribbed from my Git &amp; GitHub Secrets talk: <a href="http://zachholman.com/talk/git-github-secrets/" rel="nofollow">http:&#x2F;&#x2F;zachholman.com&#x2F;talk&#x2F;git-github-secrets&#x2F;</a><p>If you&#x27;re interested in the arcane side of Git and GitHub, you might also be interested in the follow-up talk I&#x27;ve given a few times the last half-year or so, which details a bunch of other new things: <a href="http://zachholman.com/talk/more-git-and-github-secrets/" rel="nofollow">http:&#x2F;&#x2F;zachholman.com&#x2F;talk&#x2F;more-git-and-github-secrets&#x2F;</a><p>I&#x27;m more of a fan of the second talk, myself. My favorite thing I discovered while making the second talk was the &quot;second-order-diff Git trick&quot;, which Tom Moertel came up with here: <a href="http://blog.moertel.com/posts/2013-02-18-git-second-order-diff.html" rel="nofollow">http:&#x2F;&#x2F;blog.moertel.com&#x2F;posts&#x2F;2013-02-18-git-second-order-di...</a>

&gt; Adding `#L52` to the end of a code file URL will highlight that line number.<p>You can click the line number (in the column to the left of the code) to add the fragment to the URL, and Shift+click to select a range. Easier than editing the URL directly.

One shouldn&#x27;t alias &#x27;git add . &amp;&amp; git commit&#x27; to &#x27;git ac&#x27;. You should always check what you are about to commit with &#x27;git status&#x27; and &#x27;git diff&#x27;.

One that&#x27;s missing that I&#x27;ve found rather useful: add &quot;.pibb&quot; to the end of any Gist URL to get the &quot;HTML Only&quot; version suitable for embedding in any other site. Time was, before a lot of blogging engines had GitHub integration, this was the best way to get code on your blog.

Interesting, I like the &quot;git status -sb&quot; (short, show branch tracking info) command. The query one seems a lot like &quot;git grep&quot; to me, I am not sure I understand the difference.<p>The specified &quot;git ac&quot; alias (git add . &amp;&amp; git commit) is bad news, in my book. I&#x27;ve seen people accidentally commit extra files using &quot;git add .&quot; .<p>I much prefer &quot;git add -p&quot; for tracked files; the git tab completion for the shell seems to be pretty good about picking up untracked files using &quot;git add &lt;TAB&gt;&quot; as well. (<a href="https://github.com/git/git/tree/master/contrib/completion" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;git&#x2F;git&#x2F;tree&#x2F;master&#x2F;contrib&#x2F;completion</a>)

Could someone give me a usecase for when an empty commit might be useful?

<i>Gists are an easy way to work with small bits of code without creating a fully fledged repo</i><p>What is the disadvantage of working with a &quot;fully fledged repo&quot;? Gists unecessarily fragment git workflows. For example, how do I convert my work (a git repo like all projects) into a gist? gists should have been designed as an alternative way of viewing repos, not as a slightly different species of repo.

&gt; <i>&quot;To see all of the shortcuts for given page type shift+?&quot;</i><p>Actually just ? suffices.<p>Source: the list of shortcuts shown by typing ? on a GitHub page.

Something also to know is there are multiple ways to embed images in wiki pages. There&#x27;s the standard Markdown syntax, but there&#x27;s also a syntax that allows things like specifying the height or width of the image. Example:<p><pre><code> [[ image location | height = 300px ]]</code></pre>

`git instaweb` is also one of great secrets of Git that GitHub uses very effectively.

I alias `gti` -&gt; `git`. I&#x27;m always mistyping it, not sure why.

I&#x27;d like to get more comfortable handling pull requests. Any tips on that?<p>Any time my project gets one I panic :-(

I&#x27;m digging hub! Thanks for the link to the cheat sheet.

Git.io looks really cool. Didn&#x27;t know that existed!