On this page

Project setup

Markdown

States, progress information, and outcomes of repository setup.

Project setup prepares a connected repository for Glossia. It begins after a user selects a repository and at least one target language in the New project flow.

Prerequisites

  • The account has at least one configured model.
  • The Glossia GitHub App can access the selected repository.
  • The user can create projects in the account.
  • At least one target language is selected.

States

State Meaning Available action
Pending The project has been accepted and is waiting to start. Follow progress or leave the page and return later.
Running Glossia is inspecting and updating the repository. Follow the live activity.
Completed The localization baseline was prepared and published for review. Open, review, and merge the pull request.

Projects are provisional while setup is Pending or Running. If setup cannot finish or publish a usable change, Glossia cleans up the setup environment and deletes the provisional project. The repository then becomes available in the New project flow so setup can be attempted again.

Visible progress

The setup card remains available in the new-project flow and on the project overview. It includes:

  • A state badge and progress bar.
  • A short explanation of the current state.
  • Recent repository preparation, inspection, file-change, check, and completion activity.
  • A clear failure message when setup cannot complete.

Progress is stored while the provisional project exists. A terminal failure discards both the project and its visible setup progress.

Completed result

A successful connected setup creates a dedicated branch and a pull request against the repository's default branch. The pull request contains the generated localization baseline, including GLOSSIA.md context and the smallest practical changes needed to load localized content.

Setup does not publish header-only target catalogs. When a localization framework requires target catalogs before translation, the catalogs contain the extracted source message entries with empty translation values. When target catalogs are not required yet, setup leaves them for the first translation run.

Glossia does not merge the pull request. Repository maintainers review and merge it through their normal GitHub process.

The project overview shows a setup notice while this pull request is open. The notice is removed after the pull request is merged. If the pull request is closed without being merged, the overview explains that it must be reopened before setup can be considered finished.