Skip to content
TopicTracker
From HackerNewsView original
TranslationTranslation

Ask HN: Which GitHub features are needed in a code forge before you can migrate?

A developer building a new code forge called juju.bi is asking the Hacker News community which GitHub features are essential blockers for migrating to a different platform. The forge prioritizes offline collaboration, GitHub API compatibility, and change-ID-based features (like Jujutsu's evolog). The creator is currently focusing on small teams with private repos before expanding to public repos.

Background

- A "code forge" is a platform for hosting source code and collaborating on it — GitHub, GitLab, Bitbucket, and SourceHut are examples. This post asks which features would keep a team from switching away from GitHub, the dominant forge owned by Microsoft. - Jujutsu (or "jj") is an emerging version-control system designed as a modern alternative to Git. "Change-id based features" (like jj's "evolog") track a commit's identity across edits and rebases, enabling cleaner history rewriting — something Git struggles with. - The author is building juju.bi, a new forge that works offline (many forges require a connection to browse code or file issues), is API-compatible with GitHub (so existing tools still work), and natively supports jj's model. - "S3 compatible" refers to how many cloud storage services adopt Amazon S3's API so existing software works without changes — the author wants GitHub API compatibility to work the same way. - The post is an "Ask HN", a community thread on Hacker News where someone poses a question to the tech audience.

Related stories