<?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 My Tech Blog</title><link>https://kocurkovo.cz/tags/git/</link><description>Recent content in Git on My Tech Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 09 Aug 2026 20:10:34 +0200</lastBuildDate><atom:link href="https://kocurkovo.cz/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>Git does not find commit to !fixup</title><link>https://kocurkovo.cz/posts/git-does-not-find-commit-to-fixup/</link><pubDate>Sun, 09 Aug 2026 20:10:34 +0200</pubDate><guid>https://kocurkovo.cz/posts/git-does-not-find-commit-to-fixup/</guid><description>&lt;h2 id="introduction"&gt;introduction&lt;/h2&gt;
&lt;p&gt;I started to use &lt;code&gt;--fixup&lt;/code&gt; instead of doing &amp;ldquo;fixing typo&amp;rdquo; commits in my branches and with &lt;code&gt;git rebase upstream/main --autosquash&lt;/code&gt; I prepared branch for a new MR. Receantly I discovered that in one case this worflow is breaking.&lt;/p&gt;
&lt;p&gt;Problem is having whitespace at the start of targeted commit message (see reproduction steps).&lt;/p&gt;
&lt;p&gt;After investigating &lt;code&gt;git&lt;/code&gt; source code, there is &amp;ldquo;lstrip&amp;rdquo; right after skipping the &amp;ldquo;!fixup: &amp;quot; message so when using &lt;code&gt;hashmap_get_from_hash&lt;/code&gt; it uses striped message, hence can not find the commit.&lt;/p&gt;</description></item></channel></rss>