<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Merge on Tokenise</title><link>https://tokenise.rosvetic.com/tags/merge/</link><description>Recent content in Merge on Tokenise</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Tue, 27 Oct 2026 07:07:00 +0000</lastBuildDate><atom:link href="https://tokenise.rosvetic.com/tags/merge/index.xml" rel="self" type="application/rss+xml"/><item><title>Dry-run the merge before you review: a short script for the branches your parallel agents leave behind</title><link>https://tokenise.rosvetic.com/posts/merge-dry-run-parallel-agent-branches/</link><pubDate>Tue, 27 Oct 2026 07:07:00 +0000</pubDate><guid>https://tokenise.rosvetic.com/posts/merge-dry-run-parallel-agent-branches/</guid><description>&lt;p&gt;Four worktree sessions finish within a few minutes of each other. Each reports success, each has a green test run, and each left a branch behind. Now the real work starts. Merge them in the wrong order and the second merge stops on a conflict in a file the third branch also rewrote. Merge them in a lucky order and everything lands cleanly, then the test suite fails on code nobody wrote: two agents each did something sensible in isolation, and the sum doesn&amp;rsquo;t compile.&lt;/p&gt;</description></item></channel></rss>