> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gitlocalize.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Repositories

> Connecting a repository to GitLocalize, the Add repository form, and private or organization-owned repositories.

Connecting a repository is what makes its files translatable. Click **Add repository** on your
Repositories page and fill in the form.

<Frame>
  <img src="https://mintcdn.com/gitlocalize/lskpih6euvpzy4qL/images/add-repository-form.png?fit=max&auto=format&n=lskpih6euvpzy4qL&q=85&s=d9a539ed3d00a94b9f993f48041a8ce2" alt="The Add repository form" width="1400" height="1020" data-path="images/add-repository-form.png" />
</Frame>

## Form fields

<ParamField path="Repository" required>
  The GitHub repository to localize. Only repositories the GitLocalize App can access appear here —
  see [Private repositories](#private-repositories) if yours is missing.
</ParamField>

<ParamField path="Branch">
  The branch to sync from. Defaults to `master`.
</ParamField>

<ParamField path="Source Path" required>
  Where the translatable files live. See [Paths and languages](/paths).
</ParamField>

<ParamField path="Target Path" required>
  Where GitLocalize writes translated files. The `%lang%` placeholder splits output by language. See
  [Paths and languages](/paths).
</ParamField>

<ParamField path="Source language" required>
  The language the original files are written in.
</ParamField>

<ParamField path="Target languages" required>
  The languages to translate into. More can be added later.
</ParamField>

## Private repositories

Both public and private repositories can be connected. A private repository owned by a GitHub
organization additionally requires that you hold the **Owner** role in that organization.

A repository that is private on GitHub stays private on GitLocalize — see
[Visibility](/visibility).

### When a repository doesn't appear in the list

The GitLocalize App has not been granted access to it. Click the link below the repository selector:

<Frame>
  <img src="https://mintcdn.com/gitlocalize/lskpih6euvpzy4qL/images/private-repo-app-settings-link.png?fit=max&auto=format&n=lskpih6euvpzy4qL&q=85&s=9d2761f8a523ad8f17ade167a4f95cd9" alt="The link to configure GitHub App repository access" width="1758" height="628" data-path="images/private-repo-app-settings-link.png" />
</Frame>

It opens GitHub, where you select the organization and grant the GitLocalize App access to that
specific repository:

<Frame>
  <img src="https://mintcdn.com/gitlocalize/lskpih6euvpzy4qL/images/private-repo-grant-access.png?fit=max&auto=format&n=lskpih6euvpzy4qL&q=85&s=3a08a1c83dc8509804327f28bbd22942" alt="Granting the GitLocalize App access to a repository on GitHub" width="1266" height="1292" data-path="images/private-repo-grant-access.png" />
</Frame>

## After connecting

The first [sync](/syncing) begins immediately. It pulls the matching files, parses them into
segments, and imports any translations already in the repository. On a large repository this takes
hours rather than minutes.

Imported translations that GitLocalize cannot match to a source segment arrive as
[conflicts](/conflicts) and need resolving before that file can be translated further.