gitstalk
Docs: Settings map

Settings map live

Where to find every setting, and who sees it. There are three places: a repository's Settings, an organization's Settings, and your own account Settings. Each section is its own page with its own Save, and the sections you cannot use are hidden, not greyed out.

Repository settings

Open a repository, then the Settings tab (you see it when you have a role on the repository). What the left list shows depends on your role:

acme / api owner
NameHow the repository is named on its page and in lists.
api
Description
Payments service
The owner sees all eleven sections, grouped as Repository, Code and automation, Access and Danger.
acme / api write
Someone with the write or read role sees four sections, all read-only for them. Maintainers add Actions and Deploy tokens.
Section What it is Who sees it Read more
General Rename, description, website and topics. owner Renamed and moved
Social image The picture link previews show when someone shares the repository. owner Uploads
Visibility Private, public, or internal for an organization's repository. owner Visibility
Branches Read-only: the layout is fixed. See below. anyone with a role Push is submit
Checks What counts as green, read from the stalk. Changed by a bean that edits .gitstalk/checks.yml; a repository still on checks.toml gets a Convert to YAML button (owners and maintainers). anyone with a role Checks
Approval rules beta The .gitstalk/policy.yml editor. Owners and maintainers save. anyone with a role Approval rules
Actions How workflow and automation jobs run, including the dependency cache switches. A features list shows what is on; none is switchable yet. maintainer, owner GitHub Actions
Collaborators Invite by handle, change roles, remove, and the access log (which also records approvals of held beans). owner Invite people
Secrets and variables What workflows and automations read as secrets.NAME and vars.NAME. Anyone with a role sees the names; maintainers and the owner change them. anyone with a role (where Actions run) Secrets and variables
Deploy tokens Git credentials for CI and scripts, scoped to this repository only. Read, or read and write; they expire after 7, 30, 90 or 365 days. maintainer, owner (not when archived) The start page
Danger zone Archive, transfer, delete. owner Archive, transfer, delete

The Branches page

There is nothing to change here. It shows the fixed layout:

Default branch stalk. Clones check it out and nobody pushes to it.
Landing line sprout. Beans land here; the stalk is what passed validation.
Pushable bean/*. People and agents push bean branches only.

Organization settings

Open an organization from the menu under your avatar, then Settings. Six sections: General, Members and invitations, Repository defaults, Secrets and variables, Audit log and Danger zone. Owners and admins see all six; other members see Secrets and variables and Danger zone (to leave). Each is explained on Organizations.

Account settings

Click your avatar, then Settings. Two groups, You and Access.

@coop settings
You: profile, account, emails, notifications. Access: passkeys, sessions and agents, SSH keys, tokens.
Section What it is
Public profile A picture, name, bio and website, shown on your page (<gitstalk host>/<handle>), where anyone also sees your public repositories. Without a picture you get one made from your initials.
Account Your handle, and Delete account.
Emails The address that signs you in, verified by a code.
Notifications planned Gitstalk sends no email or push today. The page lists what is planned, each with a switch that does nothing yet. Home shows invitations when you visit.
Passkeys Name them, add another, and remove the last only once you have a verified email.
Sessions and agents Every browser signed in as you and every agent connected over MCP. Ending one takes effect at once; disconnecting an agent revokes its tokens and the git credentials it minted.
SSH keys Keys that approve your machine. Only public keys are stored. The easy way to add one is /gitstalk:setup.
Tokens Personal access tokens for git over HTTPS and MCP clients without OAuth: scopes (read, collaborate, write, secrets), expiry (7 days to 1 year) and revoke. Shown once, stored only as a hash.

Sign-in, tokens and keys are explained in Accounts, tokens and keys.

Handle and deleting your account

  • Change your handle once a day. Your page, repositories and clone URLs move; links and git remotes with the old handle redirect, and nobody else can take it. You can change back to an earlier one.
  • Delete account asks you to type your handle. Your repositories are deleted with it, with their history, beans and decisions. You leave every repository you were invited to, passkeys, sessions, tokens and keys are removed, your agents disconnect at once, and your handle becomes free. If you are the only owner of an organization, add another owner or delete it first.

Uploads: pictures and icons

Your picture, an organization's icon and a repository's social image share one set of rules.

Rule Value
Formats PNG, JPEG, WebP, or GIF (first frame only).
Size Up to 2 MB, and 16 to 4096 pixels on a side.
SVG Refused, because it can carry scripts.
Processing Re-encoded at fixed sizes (a GIF keeps only its first frame) and stripped of camera and location data. Without the image service, the original is kept with that data stripped.
Shape Pictures and icons are cropped square. A social image is cropped to 2:1 (1280 by 640) after you choose it.

The social image is the preview picture shown when a link to the repository is shared in chat or on social sites.

Sources