Efficient Forged Atomic Parallel

MergeQaiPro manual Comparing three files (three-way)
Contents

Comparing three files (three-way)

Two people have edited the same file — each on their own, starting from the same version. Now both sets of work should come together. That is exactly what the three-way comparison is for: besides the two edited versions it also knows the base both started from — and can therefore tell who changed what.

7.1 The three columns

ColumnRole
Leftone edited version — stays unchanged
Basethe common starting version. It is also the result: this is where you take things over, and this file is what gets saved
Rightthe other edited version — stays unchanged
Screenshot 14: Three-way comparison with the three columns left · base · right and marked conflicts
Fig. 14 — Three-way comparison with the three columns left · base · right and marked conflicts

7.2 Change or conflict?

If only one side changed a place, the matter is clear — as a rule you want to keep that change. If both sides changed the same place differently, it is a conflict: a human has to decide. The footer counts them (“3 conflicts”) so you know how many decisions are still pending.

7.3 Resolving

Two buttons are available for each block: Left ▶ base takes the left version into the base, Base ◀ right the right one. The arrow always points at the target — the base in the middle.

Ctrl + ↓ / ↑next / previous difference
Ctrl + ←take the left side into the base
Ctrl + →take the right side into the base
Ctrl + Zundo the last resolution
Ctrl + Ssave the base (result)
💡 Why the base is the safer route
In an ordinary two-file comparison you write into one of the two original files. In a three-way comparison, by contrast, you collect the result in the base — left and right stay untouched. If something goes wrong, you still have both source versions unchanged.
An unhandled error has occurred. Reload 🗙