Repositories

A repository is the unit everything else attaches to. Creating one provisions the full surface set: code hosting, issues, pull requests, CI, documents, collections, whiteboards, and analytics. None of it is optional plumbing you switch on later.

Create a repository

From the sidebar, the command palette, or the CLI:

pln repo create my-app --repo <org>/my-app

A new repository is empty until the first push. The repository page shows the exact remote URL to use; see Pushing code.

Repository settings

Each repository has a settings page (G S from anywhere in the repo) covering:

• Default branch. The branch the code view and clones default to.
• Color. A per-repo accent used across the UI, so ten open tabs stay tellable apart.
• Feedback page. A toggle that opens a public feedback page for the repository.
• CI secrets. Encrypted values your workflows can read.
• Analytics sites. The web properties this repository measures.

Access

Repositories belong to an organisation and are visible to its members. What a member can do is governed by their role. There are no per-repository permission matrices to maintain; if your team needs harder separation, use separate organisations.

Renaming and deleting

pln repo rename --repo <org>/my-app --name my-app-v2
pln repo delete --repo <org>/my-app-v2

Renaming keeps history, issues, and settings. Deleting a repository takes everything attached to it, so Plain asks you to confirm, and agents are never allowed to do it at all.