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.
<p>(This is more or less open ended, but sorta directed to users of Jujutsu and other version control systems. However, if you have a workflow with pure Git that isn't covered by many major forges, I'd appreciate hearing them too!)</p>
<p>I'm referring to features related to version control and the presentation/behavior of repositories itself, rather than things like SPA/JS vs server-rendered HTML, etc.</p>
<p>There have been many ideas in this space, such as Tangled, GitHub's stacked PRs, forgefed, etc., but I haven't found a place where people really voice their opinions and discuss on the design itself. While stacked PRs/MRs, alternative collaboration models, etc., are definitely on-topic, I've found almost no discussion on, e.g., the presentation of tags/commits/tree/blobs themselves, which seem to be largely uniform across forges other than minor formatting differences.</p>
# What would you want from a forge?
Source: [https://lobste.rs/s/wed6lj/what_would_you_want_from_forge](https://lobste.rs/s/wed6lj/what_would_you_want_from_forge)
\(This is more or less open ended, but sorta directed to users of Jujutsu and other version control systems\. However, if you have a workflow with pure Git that isn't covered by many major forges, I'd appreciate hearing them too\!\)
I'm referring to features related to version control and the presentation/behavior of repositories itself, rather than things like SPA/JS vs server\-rendered HTML, etc\.
There have been many ideas in this space, such as Tangled, GitHub's stacked PRs, forgefed, etc\., but I haven't found a place where people really voice their opinions and discuss on the design itself\. While stacked PRs/MRs, alternative collaboration models, etc\., are definitely on\-topic, I've found almost no discussion on, e\.g\., the presentation of tags/commits/tree/blobs themselves, which seem to be largely uniform across forges other than minor formatting differences\.
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 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.