GitSocial stores your collaboration data (issues, pull requests, etc) as commits on gitmsg/* branches with structured trailers, so your data is tied to your repo, not the hosting platform.
GitSocial fetches into timeline activity from repositories added to lists or registered as forks.
brew trust gitsocial-org/tap
brew install gitsocial-org/tap/gitsocialOr using installation script
curl -fsSL https://gitsocial.org/install.sh | shscoop bucket add gitsocial https://github.com/gitsocial-org/scoop-bucket.git
scoop install gitsocialgo install github.com/gitsocial-org/gitsocial/cli/gitsocial@latestOr download a binary from Releases.
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| Document | Description |
|---|---|
| GitMsg Protocol | Core message format, headers, refs, versioning |
| Identity Verification | Decentralized trust model, attestation sources, caching |
| Notifications | Notification types, scopes, and triggers |
| 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 | — |
| 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 |
Platform issues and PRs are disabled on all mirrors. GitSocial uses its own tools for collaboration.
- 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
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 metadataAfter 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.
gitsocial pm issue create "Bug: description"
gitsocial pushFor quick questions or discussion, use the Matrix room.
MIT