---
title: Repository settings
description: Connect GitHub, choose the docs repository and branch, and configure monorepo paths.
---

Repository settings control where Radiant reads and writes your docs source.
Use them when you need to connect GitHub, change the repository, switch the
branch, or tell Radiant where the docs root lives inside a monorepo.

Only organization owners can update repository settings.

## Project types

Radiant projects can use two content hosting models.

| Project type    | What it means                                          | Best for                                                                |
| --------------- | ------------------------------------------------------ | ----------------------------------------------------------------------- |
| Radiant-managed | Radiant hosts the docs content repository for you      | Teams that want to start without managing GitHub source                 |
| GitHub-backed   | Your docs content lives in a GitHub repository you own | Teams that want Git review, local editing, CI, or direct source control |

The editor, writing agent, CLI, and deployments all work against the active docs
source for the project.

## Move Radiant-managed content to GitHub

If your project is Radiant-managed, Settings shows **Move Content to GitHub**.
Use this when you want to own the docs repository directly.

<Steps>
  <Step title="Open Settings">
    Go to the project Settings page in the Radiant dashboard.
  </Step>

<Step title="Connect GitHub">
  Connect a GitHub account if one is not already available.
</Step>

<Step title="Choose the destination account">
  Select the personal or organization GitHub account that should own the docs
  repository.
</Step>

  <Step title="Move the content">
    Radiant creates a GitHub repository, copies the docs content, and connects
    the project to the new repository.
  </Step>
</Steps>

After the move, the project becomes GitHub-backed. Future dashboard edits,
agent changes, and deployments use the connected GitHub repository.

## Connect a GitHub-backed project

For GitHub-backed projects, Settings includes GitHub connection controls.

<Steps>
  <Step title="Install the GitHub App">
    Install the Radiant GitHub App on an account that has access to the docs
    repository.
  </Step>

<Step title="Select an account">
  Choose the GitHub user or organization that owns the repository.
</Step>

<Step title="Select a repository">
  Choose the repository that contains your docs source.
</Step>

<Step title="Select a branch">
  Choose the branch Radiant should use for the live docs source.
</Step>

  <Step title="Set the docs root if needed">
    If the docs are not at the repository root, enable Monorepo and enter the
    path to the folder that contains `docs.json`.
  </Step>
</Steps>

Radiant needs GitHub App access to the selected repository. If the repository is
not listed, install or update the GitHub App access for that account.

## Monorepo path

Use the Monorepo setting when the docs root is a subfolder.

```txt
my-repo/
  apps/
  packages/
  docs/
    docs.json
    getting-started/
      quickstart.mdx
```

For this repository, set the monorepo path to:

```txt
docs
```

Do not include `docs.json` in the path. The path should point to the folder that
contains `docs.json`.

## Multiple docs sites in one monorepo

Pro organizations can connect multiple docs roots from the same repository and
branch as separate docs sites. Each connected site must use a distinct docs
root containing its own `docs.json`.

For example, one repository can publish separate sites from `docs/api` and
`docs/guides`. A push starts builds only for docs roots changed by that push.
If roots overlap, such as `docs` and `docs/api`, a change under `docs/api` can
start builds for both sites.

## After changing repository settings

Repository settings affect future builds. After updating the account,
repository, branch, or docs root, start a new deployment so the live site uses
the updated source.

Radiant shows a redeploy action after repository settings are updated.

## Common questions

<AccordionGroup>
  <Accordion title="Why can't I update repository settings?">
    Repository settings are owner-only. Ask an organization owner to make the
    change or promote you to owner.
  </Accordion>

<Accordion title="Why is my repository missing from the list?">
  The Radiant GitHub App may not have access to that repository. Update the
  GitHub App installation and include the repository.
</Accordion>

<Accordion title="What should I enter for a monorepo path?">
  Enter the path from the repository root to the folder that contains
  `docs.json`, such as `docs` or `packages/docs`. Do not use `./`, `../`, or
  include the `docs.json` filename.
</Accordion>

  <Accordion title="Does changing the branch publish immediately?">
    No. Updating repository settings changes where Radiant reads future source
    from. Start a redeploy when you want the live site to use the new source.
  </Accordion>
</AccordionGroup>

## Next steps

<Columns columns={3}>
  <Column>

<Card
  title="Deployments"
  href="/publish-and-manage/deployments"
  icon="lucide:cloud-upload"
>
  Redeploy the source.
</Card>

  </Column>
  <Column>

<Card
  title="Use the CLI"
  href="/getting-started/use-the-cli"
  icon="lucide:terminal"
>
  Preview Git changes.
</Card>

  </Column>
  <Column>

<Card
  title="Content model"
  href="/getting-started/content-model"
  icon="lucide:blocks"
>
  Understand docs root.
</Card>

  </Column>
</Columns>