About
GitSocial stores your collaboration data (issues, pull requests, etc) in your repository as commits on gitmsg/* branches with structured trailers.
Any S3-compatible bucket can be a git remote via the built-in s3:// backend and can serve a complete static site of the repo straight from the bucket.
GitSocial builds your timeline from repositories added to lists or registered as forks.
Installation
macOS / Linux with Homebrew
brew trust gitsocial-org/tap brew install gitsocial-org/tap/gitsocial
Or using installation script
curl -fsSL https://gitsocial.org/install.sh | shWindows
scoop bucket add gitsocial https://github.com/gitsocial-org/scoop-bucket.git scoop install gitsocial
Go
go install github.com/gitsocial-org/gitsocial/cli/gitsocial@latest
Or download a binary from Releases.
Quick Start
Clone your project from GitHub or any host, then from your project directory:
gitsocial import # imports issues, PRs, releases, discussions gitsocial tui # explore in the terminal
Works for S3-compatible buckets too:
gitsocial clone s3://s3.example.com/mybucket/myrepo
gitsocial remote add s3://s3.example.com/mybucket/myrepo
gitsocial push # publish repo data + a browsable website to the bucketDocumentation
Concepts
| Document | Description |
|---|---|
| GitMsg Protocol | Core message format, headers, refs, versioning |
| Identity Verification | Decentralized trust model, attestation sources, caching |
| Notifications | Notification types, scopes, and triggers |
| S3 Remote | Buckets as git remotes, canonical URLs, atomic ref updates |
| Static Site | Zero-dependency repo website served from the bucket: timeline, issues, PRs, releases, code |
Extensions
| Document | Description | Spec |
|---|---|---|
| Social | Posts, comments, lists, timeline, followers | GitSocial |
| PM | Issues, milestones, sprints, labels, boards | GitPM |
| Review | Pull requests, feedback, forks, version tracking, cross-forge scenarios | GitReview |
| Release | Releases, artifacts, checksums, signatures, SBOM | GitRelease |
| Memo | Tiered memos for knowledge as commits | — |
Clients
| Document | Description |
|---|---|
| Agent Skill | AI-assisted workflows for Claude Code, Cursor, and other agents |
| TUI | Per-view layout diagrams (see also keybindings) |
| CLI | Commands, flags, output formats |
| JSON-RPC | Client integration over stdio |
Contributing
Platform issues and PRs are disabled on all mirrors. GitSocial uses its own tools for collaboration.
Getting Started
- Install GitSocial (see Installation)
- Fork the repository on any host (GitHub, GitLab, Codeberg, or self-hosted)
- Clone your fork:
git clone https://your-host.com/you/gitsocial - Read Architecture for system design, packages, and cache layout
Submitting Pull Requests
git checkout -b feature/my-change # make changes, commit gitsocial review pr create \ --base main \ --head feature/my-change \ "Short description of change" git push origin feature/my-change # push your branch gitsocial push # push PR metadata
After your first push, request fork registration in the Matrix room so maintainers can discover your PRs and issues.
See Review for the full cross-forge PR workflow.
Reporting Bugs & Requesting Features
gitsocial pm issue create "Bug: description"
gitsocial pushFor quick questions or discussion, use the Matrix room.
License
MIT
