Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Configuration

Quick Setup

Use a preset to get started fast:

# CorvidLabs preset - sets author, org, license, template repo
fledge config init --preset corvidlabs

# Default config
fledge config init

Config File

Lives at:

~/.config/fledge/config.toml

Sections

[defaults]

Default values for new projects:

[defaults]
author = "Your Name"
github_org = "YourOrg"
license = "MIT"
KeyWhat it doesFallback
authorDefault author namegit config user.name
github_orgDefault GitHub orgPrompted
licenseDefault licenseMIT

[templates]

Where to find templates:

[templates]
paths = ["~/my-templates", "~/work/templates"]
repos = ["CorvidLabs/fledge-templates", "myorg/templates"]
KeyWhat it does
pathsLocal directories with templates
reposGitHub repos to pull templates from (owner/repo)

[github]

[github]
token = "ghp_..."

Token priority:

  1. FLEDGE_GITHUB_TOKEN env var
  2. GITHUB_TOKEN env var
  3. Config file
  4. gh auth token (GitHub CLI fallback)

Required token scopes:

FeatureScopes needed
Issues, PRs, CI checksrepo (or public_repo for public repos only)
Create PRs, push branchesrepo
Search templates/pluginspublic_repo
Publish templatesrepo, delete_repo (if republishing)

A classic token with repo covers everything. For fine-grained tokens, grant Read/Write on Contents, Pull Requests, and Issues for each repo you work with.

Full Example

[defaults]
author = "Leif"
github_org = "CorvidLabs"
license = "MIT"

[templates]
paths = ["~/.fledge/templates", "~/projects/templates"]
repos = ["CorvidLabs/fledge-templates", "my-org/my-templates"]

[github]
token = "ghp_1234567890abcdefghijklmnopqrstuvwxyz"

Environment Variables

VariableWhat it does
FLEDGE_GITHUB_TOKENGitHub token (highest priority)
GITHUB_TOKENGitHub token (fallback after FLEDGE_GITHUB_TOKEN)

If neither env var nor config is set, fledge falls back to gh auth token (GitHub CLI) automatically.

Project Configuration (fledge.toml)

Per-project settings live in fledge.toml in your project root. This file defines tasks, lanes, and project metadata. It’s created by fledge run --init or fledge templates init.

For task and lane configuration, see:

  • Lanes & Pipelines — defining lanes, step types, parallel groups, importing community lanes
  • Plugins — extending fledge with community plugins

Priority Order

When creating a project, values come from (highest to lowest):

  1. Command-line arguments
  2. Config file
  3. Git config (author only)
  4. Built-in defaults