Repositories and source browsing

Find repositories, create new ones, inspect source, and choose a clone workflow.

Find a repository

Open Repositories to search by name and filter the results by relationship:

  • repositories you own;
  • organization repositories;
  • repositories you collaborate on;
  • repositories you forked.

Select a repository to open its source, activity, issues, stack reviews, and workspace context.

Create a repository

Choose New repository from the repository list. The create form supports:

  • repository name and description;
  • personal or organization ownership;
  • public or private visibility;
  • optional README initialization.

The owner and visibility you select determine who can discover and modify the repository. If an organization is not available in the owner selector, ask an organization administrator to add you or create the repository for you.

Read source

The repository page supports a tree view, branch or bookmark selection, README rendering, commit links, file search, and file history. Use the branch selector before opening a file when you need to inspect a non-default line of development.

For text files, use preview when you want rendered Markdown and code view when you need exact source. Large or binary files are presented with bounded metadata rather than an unsafe full-page render.

Clone and connect tools

Open the repository’s Clone menu to copy the command for your preferred client. The menu keeps the repository identity and selected transport together so you do not have to reconstruct URLs by hand.

Supported paths include:

  • Git and GitHub CLI for familiar repository workflows;
  • Sapling for stack-oriented source control;
  • JJ for change-oriented local drafting.

After cloning, authenticate the client using the instructions for that tool before attempting a private repository read or push.

Access problems

If a repository is visible but source is not, or a write control is disabled, the account may have read-only access, the repository may be private, or the selected organization policy may not allow the action. The UI should preserve that distinction; retrying does not grant permissions.