Tutorial

Review and merge a change through a branch

Reword two German values and drop a key without touching main until somebody has approved it: one branch, one review request, one approval and a merge. Each step shows what the screen looks like when it is done.

10 minutes · 6 steps Updated

  1. Step 01

    Open a branch

    On the project’s Branches tab, click New branch, name it feature/cart-copy and keep main as its source — main stays exactly as it is until you merge.

    How it works: Branches

  2. Step 02

    Change values

    Switch the editor to feature/cart-copy, reword the German values you want to change and delete the key the app no longer uses — the banner counts each change against main.

    How it works: Branches

  3. Step 03

    Request a review

    When the branch is ready, click Request review in the branch banner — it turns into Review requested and the branch moves to the top of your reviewers’ queue.

    How it works: Reviews

  4. Step 04

    Approve as the reviewer

    The reviewer opens the branch from Reviews in the header, reads each change and clicks Approve, or Reject with a reason — approving is part of the Pro and Business plans.

    How it works: Reviews

  5. Step 05

    Read the merge dialog

    Click Merge in the branch banner and read the dialog before you confirm anything — it is the last place to see what main is about to gain and lose.

    Into
    The branch this merge writes into. It is main unless you pick another branch here, and the choice holds for this merge only.
    Summary, Added, Modified, Deleted
    Summary counts every change; the other three tabs list them one by one — new keys, changed values with the old text beside the new, and keys that will be gone.
    Language
    Narrows the tabs to one language. A deleted or added key belongs to every language, so it is listed under each.
    Confirm: … will be permanently deleted
    Shown when a merge into main deletes keys. The merge stays disabled until you tick it, because a deleted key takes its translations in every language with it.
    Delete branch after merge
    Removes the branch once its changes are on main. Leave it unticked to keep the branch, marked Merged, in the list.
    All operations reviewed
    Whether every change has been approved. Where the project requires approval, this line says what is still open and the merge waits for it.

    How it works: Branches

  6. Step 06

    Merge

    Tick the confirmation and click Merge into main — the reworded values are on main from then on, and the branch is listed as merged.

    How it works: Branches

Where to go from here

The documentation covers everything this walkthrough skipped, and the other tutorials take the next task from here.

Do it with your own files.

Start on the free tier with the locale files you already have.

Create your account