<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cleanup on Commentary of Takao</title><link>https://takao.blog/en/tags/cleanup/</link><description>Recent content in Cleanup on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sat, 13 Jun 2026 23:11:50 +0900</lastBuildDate><atom:link href="https://takao.blog/en/tags/cleanup/index.xml" rel="self" type="application/rss+xml"/><item><title>Cleaning Orphan Remote Branches with git fetch --prune</title><link>https://takao.blog/en/web/git-prune-clean-remote-branches/</link><pubDate>Thu, 25 Dec 2025 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/git-prune-clean-remote-branches/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post Cleaning Orphan Remote Branches with git fetch --prune" /&gt;&lt;p&gt;In modern development workflows using GitHub or GitLab, feature branches are typically deleted on the remote host as soon as their corresponding pull request (PR) is merged.&lt;/p&gt;
&lt;p&gt;However, when you run &lt;code&gt;git branch -a&lt;/code&gt; in your local terminal, you will notice that &lt;strong&gt;the references pointing to those deleted remote branches (e.g., &lt;code&gt;remotes/origin/feature-xxx&lt;/code&gt;) remain in your branch list indefinitely.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This occurs because Git does not automatically sync deletions from remote configurations to your local cache by default.&lt;/p&gt;</description></item></channel></rss>