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

Work crosses forges: pulls, issues and reviews flow both ways, and each side's crew sees them #8903

Closed opened this has it

Landed in pull #8921 · 2 runs

opened this

Part of #8900, the deep integration the owner asked for. Reuse the child forge's upstream pull path.

Done when:

3 earlier comments
commented

Parked by the crew: the run ended without a pull: declined: #8903 is blocked by #8901, which has not landed. That issue adds the forge-to-forge origin provider, and it is still open with a run in flight (torque). src/origins/providers/ has only github.ts a

commented

Reviewed pull #8921 at its head: left open: From a mirror or fork of a repository on another forge, a pull opens on the origin in one action, with its check and review state coming back here live. — A pull opens through createPull from a branch you can push to, but there is no one-action path from a mirror or fork, no fork call on the other forge, and no live check or review state.; Issues and comments read and write through, attributed to the real person. Events arrive by webhook, and a missed one is caught up. — Read and write-through with the real author is done, but there are no webhooks, and the catch-up is only the periodic sync.; A crew on either side treats a pull from the other forge as a guest under the owner's rules: it runs nothing with secrets until a person says so. — The guest rule is not in this pull.; Follow upstream works: new commits show up with one action to take them. — Following upstream is not in this pull.; Two forges test each path, including one being down for a while. — Two forges test the work paths, including an outage and recovery, but not the check, review, webhook, guest or follow-upstream paths, which do not exist yet..

commented

Left open after pull #8921 landed: 5 unticked items remain (From a mirror or fork of a repository on another forge, a pull opens on the origin in one action, with its check and review state coming back here live.; Issues and comments read and write through, attributed to the real person. Events arrive by webhook, and a missed one is caught up.; A crew on either side treats a pull from the other forge as a guest under the owner's rules: it runs nothing with secrets until a person says so.; …). 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 into #8965 (a pull opens on the origin, its state comes back, tested with the origin down), #8967 (issues and comments write through, webhook plus catch-up), #8964 (a guest pull runs nothing with secrets), #8966 (follow upstream). The two-forge tests are in each of them.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs