Repositories and collaboration

Private and public repositories

Private repositories require authorized access to browse or clone. Public repositories make source readable. To distribute an app while keeping source private, use release-only sharing.

Files, history, and branches

Files shows the selected branch’s tree. Open a file to view it; owners can commit edits or delete files. Commits shows history and commit details.

Use Merge to compare branches and check conflicts. Resolve conflicting changes before completing a merge.

orbitgit clone your-user/my-app
cd my-app
git switch -c feature/example
# Edit files, then:
orbitgit commit -am "Describe the change"
orbitgit push

Repository sharing

The Share section controls repository access; recipients find granted projects under Shared. An unlisted release link instead grants access only to published artifacts. Choose the access appropriate for your recipients.

Activity and URLs

Successful pushes that change refs update activity. Rejected or unchanged pushes do not. Lists refresh periodically and when the window regains focus.

Browser URLs can use your nickname slug. Previous owner namespaces remain valid after profile changes. Use the clone URL shown by the repository; nickname changes do not move stored objects.