Which GitHub features are needed in a code forge before you can migrate?
retained text
<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> Tags: vcs, ask
document fetched 2026-07-02 08:47