<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rebase on ARCsoft</title>
    <link>https://arcsoft.uvic.ca/tags/rebase/</link>
    <description>Recent content in Rebase on ARCsoft</description>
    <generator>Hugo</generator>
    <language>en-CA</language>
    <copyright>University of Victoria</copyright>
    <lastBuildDate>Thu, 09 Apr 2026 09:31:38 -0700</lastBuildDate>
    <atom:link href="https://arcsoft.uvic.ca/tags/rebase/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Handling Rebase when Branching off a Feature Branch</title>
      <link>https://arcsoft.uvic.ca/log/2026-03-17-handling-rebase-when-branching-off-a-feature-branch/</link>
      <pubDate>Tue, 17 Mar 2026 00:00:00 -0700</pubDate>
      <guid>https://arcsoft.uvic.ca/log/2026-03-17-handling-rebase-when-branching-off-a-feature-branch/</guid>
      <description>&lt;p&gt;Sometimes, branching a new feature off of an existing one is necessary, but it often makes rebasing feel like a nightmare. In this post, I share my personal approach to keeping a clean project history when dealing with these &amp;ldquo;grandchild&amp;rdquo; branches.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
