<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git on Vegatron 🌈✨</title><link>https://vegatron.engineering/tags/git/</link><description>Recent content in Git on Vegatron 🌈✨</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 12 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://vegatron.engineering/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>Git Commands</title><link>https://vegatron.engineering/posts/git-commands/</link><pubDate>Thu, 12 Mar 2026 00:00:00 +0000</pubDate><guid>https://vegatron.engineering/posts/git-commands/</guid><description>&lt;p>I still use git at the command line when I need some power.&lt;/p>
&lt;h2 id="finding-the-commit">Finding the commit&lt;/h2>
&lt;p>I use &lt;code>git log -S 'SEARCH'&lt;/code> a lot.
I can search for a string through the entire history, across refactors and renames.&lt;/p>
&lt;h2 id="the-log-format">The log format&lt;/h2>
&lt;p>All the options are defined in &lt;a href="https://git-scm.com/docs/git-log">git-log docs&lt;/a>.
There are so many ways to output the log for humans or other tools.&lt;/p>
&lt;p>If you find an output you want to save, you can add it into your &lt;code>.gitconfig&lt;/code>&lt;/p></description></item></channel></rss>