Public: anyone can read this; the crew can change it.

Connecting a friend's forge is obvious and works with forges on an older release #9388

Closed opened this has it

Landed in pull #9390

opened this

The owner, 2026-11-03: "im not seeing the forge to forge integration. how do i add my friend's forge as an origin. i have an account on his and want to bring apps here". The feature shipped (#8908, #8920, #8904) and can't be found or used:

  • /settings/origins names only "For Forgejo or Gitea" and "Forgejo / Gitea, one click"; the word forge as a kind appears nowhere. /bring says nothing about connecting first until it fails.
  • A real friend's forge, forge-apps.benjivers.com, runs 0.5.29: GET /api/v1/version answers no_route, nodeinfo 404, so discover refuses it. It does answer /api/v1/health and /api/v1/here. Everyone's forge will lag; a new-only handshake locks out exactly these friends.

Done when:

2 earlier comments
commented

Reviewed pull #9390 at its head: ticked Origins leads with "Another forge": address and token, or sign in, with a line saying where to get the token on theirs.; /bring with a link to an unconnected forge offers connect in place, keeps the link, and comes back to it. Private repositories work with the token.. left open: discover recognises any forge version through what old ones already answer, and provider forge lists repositories on an old forge without /api/v1/user/repos in the Gitea shape. A test runs against a fixture of a 0.5.x forge's answers. If one really can't, the error says which version it needs. — The fixture is written from this repo, not captured from a real 0.5.x forge, and there is no error naming a required version.; A cold reader with an account on a friend's forge brings an app in 2 minutes, proven against forge-apps.benjivers.com read-only. — Not proven against that host, which the build sandbox cannot reach..

commented

Left open after pull #9390 landed: 2 unticked items remain (discover recognises any forge version through what old ones already answer, and provider forge lists repositories on an old forge without /api/v1/user/repos in the Gitea shape. A test runs against a fixture of a 0.5.x forge's answers. If one really can't, the error says which version it needs.; A cold reader with an account on a friend's forge brings an app in 2 minutes, proven against forge-apps.benjivers.com read-only.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

commented

Split by box. The pull's work is shipped. The fixture-backed support for old forges is #9456. The 2-minute cold-reader proof against forge-apps.benjivers.com is #9457, held behind the Later gate because no sandboxed builder can reach that host and it needs a person with an account there.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs