A discussion on Lobsters asks which GitHub features are essential blockers for migrating to a different code forge, with the author building a forge called juju.bi focused on offline collaboration, GitHub API compatibility, and change-id based features.
<p>Which GitHub features would you consider a blocker for migrating to a different code forge, and in what order do you prioritize them?</p>
<p><strong>Context:</strong></p>
<p>I am heads down building a code forge (<a href="https://juju.bi" rel="ugc">https://juju.bi</a>) based on three ideas:</p>
<ul>
<li>Code collaboration part should work offline</li>
<li>Should be compatible with GitHub API (like how some services are considered S3 compatible)</li>
<li>Support <code>change-id</code> based features (ex: Jujutsu's evolog)</li>
</ul>
<p>I shipped a super-early version that I am currently dogfooding. <a href="https://juju.bi/changelog/2026-07-01-alpha-release" rel="ugc">https://juju.bi/changelog/2026-07-01-alpha-release</a></p>
<p>I am currently focused on improving the experience for small teams working on private repos. I would like to polish the overall product before thinking about public repos. (A lot of great forges exist for public repos right now).</p>
# Which GitHub features are needed in a code forge before you can migrate?
Source: [https://lobste.rs/s/w01x4p/which_github_features_are_needed_code](https://lobste.rs/s/w01x4p/which_github_features_are_needed_code)
Which GitHub features would you consider a blocker for migrating to a different code forge, and in what order do you prioritize them?
**Context:**
I am heads down building a code forge \([https://juju\.bi](https://juju.bi/)\) based on three ideas:
- Code collaboration part should work offline
- Should be compatible with GitHub API \(like how some services are considered S3 compatible\)
- Support`change\-id`based features \(ex: Jujutsu's evolog\)
I shipped a super\-early version that I am currently dogfooding\.[https://juju\.bi/changelog/2026\-07\-01\-alpha\-release](https://juju.bi/changelog/2026-07-01-alpha-release)
I am currently focused on improving the experience for small teams working on private repos\. I would like to polish the overall product before thinking about public repos\. \(A lot of great forges exist for public repos right now\)\.
A discussion thread on Lobsters asking developers what features they would like to see in a code forge, particularly regarding version control presentation and collaboration models, referencing tools like Jujutsu and Git.
The article discusses the decision to migrate from GitHub to self-hosted Forgejo, citing concerns over data ownership, reliability, and AI data collection practices. It highlights similar moves by the Dutch government and details the technical setup of a personal Forgejo instance.
The article explores the fragmentation of code forges as projects leave GitHub, introduces a tool to unify git activity heatmaps across platforms, and discusses trust systems to combat AI-generated spam contributions.
Forge is a new CLI and Go library that unifies interactions across GitHub, GitLab, Bitbucket, and Gitea/Forgejo with a single interface and automatic forge detection.
The article discusses the growing dissatisfaction with GitHub's reliability and proposes Tangled, a decentralized Git forge built on the AT Protocol, as a promising alternative that combines centralized convenience with user-owned data.