Home Getting Started The run finished — how do I check what it changed?

The run finished — how do I check what it changed?

Last updated on Sep 16, 2026

The run is complete and globalize.now pushed the results to your repo. Here's how to review and verify before you call it done.

Where the changes land

Everything arrives on a globalize branch in your repo, for you to review and merge like any other change. Nothing lands on your default branch without you.

What you should see

/messages          (or /locales — depends on your i18n library)
  en.json          ← your source strings, all extracted
  es.json          ← translated
  de.json          ← translated
  fr.json          ← translated

Plus modified component files (hardcoded strings replaced with t("checkout.submit")-style calls), the i18n provider wrapped around your app entry, and a new library config.

You may also see the globalize skill files added — plain-text instructions that set up your coding agent to work with globalize. They're expected, not junk.

If you don't see any of this, check the job status in the app — see "Translation job errors and failures".

A five-minute review before you merge

  1. Open the source locale file — the values should read like your actual UI text, not fragments or garbled output.

  2. Spot-check a few components — t("some.key") calls where inline text used to be, consistent key naming (checkout.submit_button, not a mix of styles), no leftover hardcoded strings in converted files.

  3. Check the language files contain actual translations, and all the languages you selected are present.

Run it locally

  1. Pull the branch — or ask your coding agent to pull and run the app

  2. Start your dev server (npm run dev or your usual command)

  3. Switch languages with the switcher and click through a few pages

Text should change language and nothing should break. If the switcher is missing or switching crashes the app, chat with us in the app — that usually means the provider wiring needs a fix on our side.

If something looks off

Don't merge — your default branch is untouched. Fix specific files on the branch, or tell us in chat what looks wrong. If entire strings were missed, see "My translation PR looks wrong: what do I do?".

Merge, then test the ongoing loop

Merge the branch, then make a small text change and push it:

git add .
git commit -m "test: trigger translation"
git push

Within a few minutes you should see a pull request from globalize.now with the new string translated in every language. Merge it — that loop is now your localization process. No further manual steps.