<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tools on Alra</title><link>https://alra.dev/categories/tools/</link><description>Recent content in Tools on Alra</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 29 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://alra.dev/categories/tools/index.xml" rel="self" type="application/rss+xml"/><item><title>Git Workflow: from commit to rebase, without the headaches</title><link>https://alra.dev/posts/git-workflow-from-commit-to-rebase-without-the-headaches/</link><pubDate>Wed, 29 Jul 2026 00:00:00 +0000</pubDate><guid>https://alra.dev/posts/git-workflow-from-commit-to-rebase-without-the-headaches/</guid><description>&lt;p&gt;If you&amp;rsquo;ve ever worked on a software project with a team, you know Git stopped being &amp;ldquo;just a technical detail&amp;rdquo; a long time ago - it&amp;rsquo;s part of how you think through your day-to-day work. Understanding &lt;strong&gt;how&lt;/strong&gt; and &lt;strong&gt;when&lt;/strong&gt; to use each command is what separates people who just &amp;ldquo;survive&amp;rdquo; Git from people who actually flow with it.&lt;/p&gt;
&lt;p&gt;In this article I want to go beyond the basics (&lt;code&gt;init&lt;/code&gt;, &lt;code&gt;add&lt;/code&gt;, &lt;code&gt;commit&lt;/code&gt;, &lt;code&gt;push&lt;/code&gt;) and walk through the workflow I actually use day to day, including &lt;strong&gt;feature branches&lt;/strong&gt;, &lt;strong&gt;rebase&lt;/strong&gt;, and the most common error fixes that show up in real work.&lt;/p&gt;</description></item></channel></rss>