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.
Open Settings
Go to the project Settings page in the Radiant dashboard.
Connect GitHub
Connect a GitHub account if one is not already available.
Choose the destination account
Select the personal or organization GitHub account that should own the docs repository.
Move the content
Radiant creates a GitHub repository, copies the docs content, and connects the project to the new repository.
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.
Install the GitHub App
Install the Radiant GitHub App on an account that has access to the docs repository.
Select an account
Choose the GitHub user or organization that owns the repository.
Select a repository
Choose the repository that contains your docs source.
Select a branch
Choose the branch Radiant should use for the live docs source.
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.
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.
For this repository, set the monorepo path to:
Do not include docs.json in the path. The path should point to the folder that
contains docs.json.
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.