Add git-swarm to Tools - #46
Merged
Merged
Conversation
crtahlin
force-pushed
the
add-git-swarm
branch
from
August 20, 2026 11:54
aea8a22 to
6c33373
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds git-swarm to the Tools section.
What it is. A Git remote helper that makes Swarm a first-class Git remote:
git push bzz://…andgit clone bzz://…work with stock Git once the helper is onPATH. Packfiles are stored as content-addressed Swarm chunks; the mutable "current tip ofmain" problem is solved with a signed Swarm feed, which is the one thing Git itself does not provide. Shipsgit-remote-bzzandgit-remote-swarmbinaries.Status, stated plainly. Phase 0 (clone a repo from a public gateway with stock Git, no plugin) and Phase 1 (the remote helper, with a documented on-Swarm format spec) are both complete, and the static web viewer works. Git-native issues, ACT private repos and ecosystem mirroring are planned and marked as such in the README. The repository describes itself as a proof of concept; the push/clone path is nonetheless working and published, not aspirational.
Verification. Both published feeds resolve today: the viewer at
02a7f5a1…returns the rendered viewer, and the repository feed atde4a9c97…returns validswarm-git/1JSON with refs. These survived the expiry of the project's original postage batch because the content was republished onto a durable batch.Checklist
MITLICENSE, last push 2026-08-10.README.md/archived.md; no open PR or issue for it.awesome-lintpasses: 0 errors, and only the two spelling warnings already present onmain.Disclosure: I am a CODEOWNER of this repository and this is my own project, so I will not be reviewing it — it needs @Cafe137 or @yjkellyjoo.