What git is for
- Org-scoped repository hub — list and open repos for admin + customer Clerk organizations
- CI visibility — Depot-backed build runs (list, filter, run detail) as the primary operations surface
- External product links — issues and feedback stay in Linear / Productlane rather than a built-in tracker
- Future SSH keys — settings for key upload; no custom end-user profile page required for customers
What it is not (yet)
- Live git hosting / code browser (frontend shell first; git surface lands later)
- Public self-serve repo creation at arbitrary scale (~tens of repos, not millions)
- Built-in discussions or forum features (postponed)
Stack (current shell)
How it fits the suite
Status
The frontend shell is early access: sign-in and tour paths ship with mock repo / CI data. Git hosting and live Depot CI are not fully wired yet. Until then:- Source: github.com/solvedggorg/git
- Org overview: solved.gg/projects
What to expect next in these docs
- Access model (Clerk orgs, who can sign in)
- Repo list and repo hub
- CI runs and Depot integration
- SSH keys and settings
- Operator / deploy notes for the Worker