---
title: "Repositories"
description: "Manage repositories and configure repository settings in Forkline."
section: "configuration"
url: "https://forkline.dev/docs/repositories"
markdown: "https://forkline.dev/docs/repositories.md"
source: "src/content/docs/repositories.md"
---

# Repositories

Repositories in Forkline link your git repositories to runners, storing configuration, secrets, and automation settings.

## Overview

A Forkline repository represents a connection between:

- **Your git repository** (GitHub, GitLab, Forgejo)
- **Runner configuration** (size, model, setup scripts)
- **Secrets** (API keys, credentials)
- **Automation settings** (webhooks, auto-fix)

> **Info**: Repositories sync automatically from your git connectors. Activate them to start runners.

## How Repositories Work

### Automatic Sync

When you connect a git provider, Forkline automatically discovers your repositories:

1. Connect a git provider on the **Git Providers** page
2. Forkline syncs accessible repositories
3. Repositories appear on the **Repositories** page as "Available"

### Repository States

| State | Description | Actions Available |
|-------|-------------|-------------------|
| Available | Synced but not activated | Activate to enable runners |
| Active | Ready for runners | Start runners, configure settings |
| Deactivated | Disabled, pending deletion | Reactivate or delete permanently |

![Repositories page - available repository](https://forkline.dev/docs/screenshots/repositories/repository-available.webp)

## Activating a Repository

1. Navigate to **Repositories**
2. Find the repository in the list
3. Click the **Activate** button

![Repository activation button](https://forkline.dev/docs/screenshots/repo-toggle.webp)

Once activated, you can:
- Start runners
- Configure settings
- Add secrets
- Enable automation

> **Note**: Only activated repositories can run tasks. Available repositories are synced but not configured.

## Repository Settings

Access settings for an active repository:

1. Click **Settings** on the repository card
2. Configure:
   - Default runner size
   - Default model
   - Automation options

![Repository settings modal - General tab](https://forkline.dev/docs/screenshots/repositories/repository-settings-general.webp)

The settings modal has three tabs:

- **General**: Configure default runner size and model
- **Automation**: Enable auto-fix features and set trigger policies
- **Secrets**: Store sensitive credentials

| Setting | Description | Default |
|---------|-------------|---------|
| Default Runner Size | Size for new runners | Account default |
| Default Model | AI model for runners | Account default |

## Deactivating a Repository

When you deactivate a repository:

1. Click the repository status button to deactivate it
2. Confirm the deactivation

**Effects:**
- All active runners are stopped
- Configuration is retained for 7 days
- After 7 days, configuration is permanently deleted

> **Tip**: Deactivated repositories show as "Available" and can be reactivated within 7 days.

## Permanently Deleting

To permanently remove a repository's configuration:

1. Find a deactivated repository
2. Click **Delete config**
3. Confirm the action

> **Warning**: This permanently removes the repository configuration, secrets, and any remaining runners. Your git repository is NOT affected.

## Next Steps

- [Configure repository secrets](https://forkline.dev/docs/repositories/secrets)
- [Set up automation scripts](https://forkline.dev/docs/repositories/setup-scripts)
- [Start a runner](https://forkline.dev/docs/runners/starting)