GitWorkshop
GitWorkshop is the most complete browser client for the ngit ecosystem. It is an interface to open protocols, not a forge that owns your repository.
What it is good for
- discovering NIP-34 repositories;
- browsing commits, trees, and individual files without a full clone;
- reading and managing issues and pull requests;
- inline code review and threaded discussion;
- inspecting signed repository state across servers;
- viewing CI runs and deciding which coordinator identities to trust; and
- using Nostr signers from the browser or supported app environments.
What stays in the CLI docs
GitWorkshop should have concise, task-based UI documentation where an interface is not self-explanatory: signing, trust, multi-maintainer state, merge behaviour, and recovery from partial server data. It does not need a prose page for every button. Terminal commands and automation contracts remain in the ngit reference.
A shared mental model
An issue opened in GitWorkshop and an issue opened with ngit issue create are the same kind of signed protocol object. A pull request checked out with ngit is the same proposal reviewed in the browser. Users can move between interfaces without migrating data or asking a platform for an export.