Managing estates

Updated Jul 27, 2026

Concordat tracks platform-standards repositories, referred to as estates, in $XDG_CONFIG_HOME/concordat/config.yaml (~/.config/concordat/config.yaml on most systems). Each estate entry records an alias, the managed github_owner, the Git URL for the platform-standards repository, the OpenTofu inventory path, and the default branch. The CLI uses the active estate to determine where enrolment PRs should be opened.

  • Bootstrap a new estate from the bundled template:
  uv run concordat estate init core [email protected]:example/platform-standards.git \
    --github-owner example \
    --github-token "$GITHUB_TOKEN"
  • The CLI copies the platform-standards directory into a temporary Git repo, commits the initial contents, and pushes to the provided remote.
  • --github-owner is required when the remote URL is not hosted on GitHub. When omitted, the CLI infers the owner from the repository slug, prompts for confirmation, and stores it so concordat enrol can enforce the namespace guard.
  • When the target repository does not exist, Concordat prompts before using the GitHub API (via github3.py) to create it. Pass --yes to skip all prompts in scripted environments.

  • Initialization aborts if the repository already contains commits.

  • List the configured estates and their remotes:

  uv run concordat estate ls
  • Show the repositories that an estate currently manages. Without an argument, the CLI uses the active estate:
  uv run concordat estate show
  uv run concordat estate show sandbox
  • Switch the active estate:
  uv run concordat estate use sandbox