Tech Insights

<p>Create image visualizations of git commands on your repo </p>

<p>To push up to a certain commit you can use <code>git push &lt;remotename&gt; &lt;commit SHA&gt;:&lt;remotebranchname&gt;</code>. You can combine it with <code>git rebase -i</code> too! Very useful for </p>

<p>You can use git log to search when a given string matches an entry in there and also see from which branch/tag they matched and even see the patch inline by using <code>git log -S 'string-for-match' --source --all -p</code>. <code>-S</code> is used to provide the search string, <code>--source --all</code> will properly format ref names to their respective source branch/tag and <code>-p</code> will allow you to see the patch inline. The last flag can be omitted if one just wants to see the list of commits and could go through each one individually by grabbing their hash and using a <code>git show</code> command afterwards. See for more</p>

<p>Fixing insufficient git permissions error </p>

<p>If you're pair programming, you can add <code>Co-authored-by: Author Name &lt;author@&gt;</code> for all developers in the pairing session to the commit body and they'll be recognized as co-commiters. Works for Github and Gitlab </p>

<p>Git has --ours and --theirs for handling binary file conflicts </p>

<p>Oh Shit, Git!?! </p>

<p>You can cherry-pick a range of commits at once </p>

<p>Conventional Comments </p>

<p>The Standard of Code Review - Google Engineering Practices </p>

<p>If you're using Github's hub extension, try using <code>hub sync</code>, or <code>git sync</code> (if you've set <code>alias git=hub</code>). It'll update your local branches, saving you a few minutes going through different local branches and updating one-by-one</p>

<p>You can gitignore files locally by editing <code>.git/info/exclude</code></p>

<p>How to fetch all Git branches </p>

<p>How to Write a Git Commit Message </p>

<p>How to specify different SSH keys for git push for a given domain: </p>

<p>How to Make Your Code Reviewer Fall in Love with You </p>

<p>Copying a commit from a repo into another </p>

<p>Copying commits from a repository into another </p>

Oh shit, git! Some of the most common things that can go wrong when working with git.

<p>9 useful tricks of git branch: </p>

<p>Always good to remember: use <code>git diff -w</code> to ignore whitespace. Very useful for finding bad edits on commits that should only affect indentation! #Documentation/git-diff.txt--w</p>

<p>Personalizing GIT: Aliasing commands </p>

<p>Git From Beginner To Advanced. </p>

<p>Incremental PRs: a new GitHub workflow for the Gatsby Cloud team </p>