{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihhecemph7aqkxy735x7xkkuvawc2q2yx7qcwh67m5rqfclv6dmoe",
    "uri": "at://did:plc:wvbzyoyqr6q5pgezutm4sf3v/app.bsky.feed.post/3mma6zs26pff2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreieoxcldglwex7qktrgi7ojrrlnbrkctystv7zh5b5l5zbikpor7pm"
    },
    "mimeType": "image/png",
    "size": 1995
  },
  "path": "/s/wed6lj/what_would_you_want_from_forge",
  "publishedAt": "2026-05-19T14:29:40.000Z",
  "site": "https://lobste.rs",
  "tags": [
    "design",
    "vcs",
    "ask"
  ],
  "textContent": "(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!)\n\nI'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.\n\nThere 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.",
  "title": "What would you want from a forge?"
}