Repositories and access

Repositories

Create a repository, choose who can read and write it, set its landing rules, and delete it.

Create#

WhereHow
WebNew repository: an owner (you or one of your organizations), a name, Private or Public
CLIyoneda repo create <name> [--owner <org>] [--public]
APIPOST /api/v1/repos
MCPrepo_create {name, files?, policy?} on the account endpoint (needs repo:admin)

Each repository has an id like r3f1c0d2e4a5b6c7d8e9f used in Git URLs and the API, and a name shown in the app. To bring in existing code, see Import a repository.

Visibility#

Shell
yoneda repo visibility <id> public    # anyone reads, no sign-in; only members write
yoneda repo visibility <id> private

Or Settings → Visibility. A public repository is cloned by stock Git with no credentials and listed on Explore. A private repository answers "not found" to everyone who is not a member. Only the owner (for an organization's repository, an organization owner) changes visibility; the change applies within a second.

Members#

Add accounts or organization teams under Settings → Members, with a role:

RoleCan
readRead and clone
writeAlso commit, push working branches and post checks
landAlso review and land on protected branches
adminAlso act as the owner, except deleting the repository and managing admins

A team is added as team:<org>/<team>. Removing a member refuses their next request. A member's personal token holds only what both its scopes and the member's role allow.

Landing rules#

Settings → Landing rules (or yoneda policy set '<json>') sets the policy for the protected branches main, release and release/*:

JSON
{
  "approvals": 1,
  "required_checks": ["test"],
  "runners": {
    "test": { "command": ["npm", "test"], "timeout_seconds": 600 }
  },
  "auto_approve": ["docs", "formatting", "comment_only"]
}
KeyMeaning
approvalsApprovals of the head commit needed to land, from accounts other than its author
required_checksChecks that must pass on the head
runnersChecks the platform runs itself: a command, or a model call; see Landings
auto_approveKinds of change that count as approved: docs, formatting, comment_only. A pushed commit is classified just after the push (up to 32 commits and 200 files a push), so it needs an approval until then, and one past those limits always does
secret_allowAccepted secret-scan false positives; see Security

A command runner may name paths (up to 32): only files at or under them are shipped to its check container. Without paths the whole tree ships. Either way the checked commit's tree is shipped without history.

yoneda policy show prints the current rules. Unprotected branches move with write, like any Git branch.

Settings#

SectionWhat it holds
Landing rules, ChecksThe policy above; the checks the platform runs and who may post each
Secret exceptionsAccepted secret-scan false positives
WebhooksSigned event deliveries; see Webhooks
PluginsManaged review agents and third-party plugins
Members, Repository tokensWho can use the repository; see Tokens and access
Large files (LFS)The LFS storage quota; see Git LFS
Visibility, ConnectPublic or private; clone commands and the repository id
Delete repositoryDelete it, typing its name to confirm

Delete#

Shell
yoneda repo delete <id> --confirm <name>

Or Settings → Delete repository. The name must be typed to confirm. A repository with forks cannot be deleted until they are.

Where deleted repositories are kept for a time, their owner can restore one from Account → Recently deleted. An organization's are on its page, for its owners.

To delete one for good before its time is up, use Delete on its row, or Delete all when several are listed. This can't be undone: nothing restores it afterwards. A repository under a legal hold is refused until the hold is released. This takes the owner, signed in: a token can delete a repository and restore it, but never delete it for good, so the time to restore survives a stolen token.