# IPFS remote bridge for Git: version 1.0.0 is now available

**URL:** https://discuss.ipfs.tech/t/ipfs-remote-bridge-for-git-version-1-0-0-is-now-available/19897
**Category:** Ecosystem and Usage
**Created:** [November 20, 2025, 9:52am UTC](https://discuss.ipfs.tech/t/ipfs-remote-bridge-for-git-version-1-0-0-is-now-available/19897 "2025-11-20T09:52:39Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![twdragon](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/twdragon/32/4073_2.png) [@twdragon](https://discuss.ipfs.tech/u/twdragon)
#### Post date: [November 20, 2025, 9:52am UTC](https://discuss.ipfs.tech/t/ipfs-remote-bridge-for-git-version-1-0-0-is-now-available/19897/1 "2025-11-20T09:52:39Z")

</div>

Hello everyone!

After more than a year, I introduced a significant UX update to the [**Git IPFS Remote Bridge**](https://github.com/ElettraSciComp/Git-IPFS-Remote-Bridge) project that I maintain, and now the version `1.0.0` is here!

The comprehensive Git toolset for IPFS seamlessly adds the `ipfs://` pseudo-protocol prefix for Git remotes, allowing HTTP cloning from the CID, direct push with automatic remote CID adjustment, and, as a main feature, full support of IPNS names for acquiring and pushing with automatic local public key presence detection. The provided `git-ipfs` user interaction tool has its own CLI with options to control the process from the IPFS side. The [PPA package](https://launchpad.net/~twdragon/+archive/ubuntu/ipfs) is fully debianised, and it now provides a descriptive Git-styled **man** page.

Now, the typical workflow with a Git repository published on the IPFS network via an IPNS name on the machine where the Kubo API runs at `http://127.0.0.1:5001` is as simple as:

```bash
# k51 ******** is a valid IPNS name with the key existing on the current machine
git ipfs clone k51 ********./dir-name http://127.0.0.1 5001
cd dir-name
# ...
# ...
# git add .
git commit -m "..."
git push

```

…and that’s it! The repository is now pushed into the IPFS network and published via the specified key.

Opinions, evaluations, and contributions are strongly encouraged!

> **[GitHub - ElettraSciComp/Git-IPFS-Remote-Bridge: Git IPFS Remote Bridge](https://github.com/ElettraSciComp/Git-IPFS-Remote-Bridge)**
>
> Git IPFS Remote Bridge

---

<div class="post-metadata">

### Author: ![twdragon](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/twdragon/32/4073_2.png) [@twdragon](https://discuss.ipfs.tech/u/twdragon)
#### Post date: [November 21, 2025, 9:28am UTC](https://discuss.ipfs.tech/t/ipfs-remote-bridge-for-git-version-1-0-0-is-now-available/19897/2 "2025-11-21T09:28:53Z")

</div>

PyPI package is WIP now too

---

<div class="post-metadata">

### Author: ![twdragon](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/twdragon/32/4073_2.png) [@twdragon](https://discuss.ipfs.tech/u/twdragon)
#### Post date: [November 25, 2025, 10:00am UTC](https://discuss.ipfs.tech/t/ipfs-remote-bridge-for-git-version-1-0-0-is-now-available/19897/3 "2025-11-25T10:00:47Z")

</div>

[PyPI package](https://pypi.org/project/git-ipfs-remote-bridge/), compatible with Windows, is now available
