PR Flow
How it works
Section titled “How it works”your-last-translation-tool uses the gh CLI to create and update GitHub PRs. No GitHub tokens are stored in the app — authentication is delegated entirely to gh auth.
When you click Push & open PR, the app:
- Commits any unsaved changes to your local branch.
- Runs
git push origin <branch>to push to GitHub. - Runs
gh pr create(orgh pr editif a PR for this branch already exists) with the generated title and body. - Opens the PR URL in your default browser.
Required gh scopes
Section titled “Required gh scopes”The default gh auth login flow grants the repo scope, which covers everything the app needs:
| Action | Scope needed |
|---|---|
| Push commits | repo |
| Create PRs | repo |
| List PRs | repo |
| Read org repos | read:org (needed for org repos) |
If the app shows a “missing scope” error, run:
gh auth refresh -s repo,read:orgThen click Recheck in the app.
Creating a new PR
Section titled “Creating a new PR”- Make your edits in the translation editor.
- Click Push & open PR.
- The app suggests a PR title based on the branch name and changed keys. Edit it if needed.
- Click Create PR. The PR opens in your browser.
Updating an existing PR
Section titled “Updating an existing PR”If your current branch already has an open PR, the app shows Push to PR instead of Create PR. Clicking it pushes your latest commits to the same PR — no new PR is opened.
Branch naming
Section titled “Branch naming”By default, new translation branches are prefixed with translations/ (e.g., translations/uk-homepage-keys). You can change the prefix per project in .translations.json via the branchPrefix field.