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

One forge connects to another as an origin: bring in a friend's app, and stay connected #8900

Closed opened this has it

Landed in pull #8908

opened this

The owner, 2026-11-02: "how do i add my friend's forge as an origin so i can bring in one of his apps". Origins know GitHub, Forgejo and Gitea only. discover in src/origins/discover.ts probes nodeinfo and /api/v1/version, and this forge answers 404 for /api/v1/version (checked). So a forge can't be connected to another forge; the only way is Migrate with a public URL.

Done when:

3 earlier comments
commented

The owner, 2026-11-02: "thats like the main point of this. i need to be able to add forges as origins then we can deeply integrate." This is the top priority on the forge. This issue now tracks the whole; pieces follow in order, each landing alone. Read docs/ORIGINS.md and the child forge's upstream path (provenance, a pull a child proposes upstream) first: reuse it rather than building a second one.

commented

Reviewed pull #8908 at its head: left open: Connect at /settings/origins takes a forge's URL, recognises it as a forge, and signs in through its OAuth or a pasted token; a test runs two forges against each other. — Only the pasted token works; there is no OAuth sign-in.; The picker lists that account's repositories and apps, and a private one comes across with the credential (never in argv or config). — Repositories are listed and a private one mirrors, but apps are not listed and org repositories are missing.; Migrate brings an app whole: code, how it runs and its build, with the app running here. Its data and secrets never come by default, and the page says what didn't come. — Only code and history come across; how the app runs and its build are not brought.; Follow upstream works between forges, so he can send improvements and I can take his. A pull can go back to his forge. — Not implemented.; The first-time path is one page: paste the link to the app, sign in if asked, done. — Not implemented..

commented

Left open after pull #8908 landed: 5 unticked items remain (Connect at /settings/origins takes a forge's URL, recognises it as a forge, and signs in through its OAuth or a pasted token; a test runs two forges against each other.; The picker lists that account's repositories and apps, and a private one comes across with the credential (never in argv or config).; Migrate brings an app whole: code, how it runs and its build, with the app running here. Its data and secrets never come by default, and the page says what didn't come.; …). 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. Already on main: the forge provider with OAuth (src/origins/providers/forge.ts, test/forge-origin-oauth.test.ts) and the bring page, which says what didn't come and watches the first deploy (src/web/pages/bring.ts, #8919). What's left: #8963 (a private repo's credential never in argv, config or logs), #8965 (a pull goes back to the origin forge), #8966 (follow upstream between forges).

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs