Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vers.sh/llms.txt

Use this file to discover all available pages before exploring further.

​
vers repo visibility

Toggle a repository’s is_public flag. Public repos are discoverable and forkable by any authenticated Vers user. Private repos are only visible to members of your org.

​
Synopsis

vers repo visibility <name> --public             # make public
vers repo visibility <name> --public=false       # make private

​
Description

Flips the visibility flag on an existing repo. No commits are moved, copied, or rebuilt, the only thing that changes is who can list and fork the repo. Once public, the repo appears in GET /api/v1/public/repositories and is reachable as your-org/repo-name:tag from anywhere.
Making a repo public exposes the commits it currently tags, and will continue to expose any commit you tag there while it’s public. Don’t publish repos whose commits contain API keys, SSH private keys, ~/.netrc contents, database credentials, or anything else secret. A Vers commit is a full filesystem + memory snapshot, treat it like a public Docker image with extra state. If you’re unsure, keep it private and fork selectively when you need to share.

​
Options

OptionDescription
--publicSet to public. Use --public=false to make private.

​
Examples

​
Publish a repo

vers repo visibility demos --public
# ✓ Repository 'demos' is now public

​
Take it back

vers repo visibility demos --public=false
# ✓ Repository 'demos' is now private
Once made private again, any existing forks other orgs already made remain in those orgs (they’re independent copies). The repo just stops being discoverable/forkable by new users.

​
See Also