Guest pulls

A pull whose author lives on another forge — brought in from the origin, or whose head lives in a fork there — is a guest (src/origins/guest.ts).

Until a person who can write the repository approves it once:

(AppsRuntime.secretsFor in src/apps/runtime.ts), and its terminal holds none either: it asks the same reader;

the app's previews are set to; the deploy's log and the pill on the preview say so ("This preview uses empty data until a writer approves the pull"), and the approval's own deploy seeds the data as configured;

an autonomous repository, where the crew's reviewer reads every stranger's pull first (stranger pulls).

Its check needs nothing here: a check never carries the repository's secrets, a guest's or anyone's (src/checks/service.ts builds its environment from the forge's own names only).

test/guest-pull-env.test.ts proves both from the processes themselves: a guest's real check prints its environment and none of the app's variables or a forge token is in it, before approval and after; its real preview answers with neither until a writer approves, then with both.

The pull page says it is a guest to everyone; writers see Approve this guest, a same-origin form posting to /:owner/:name/pulls/:number/approve-guest. In the terminal the pull screen says the same, and a writer presses G. Both call approveGuestPull (src/actions/pulls.ts), which announces pull.guest_approved: open pages hear it live, and the preview starts again holding the app's variables.

The approval is per pull, not per head. It is kept in guest_approval and stays when the guest pushes again: every later head of that pull runs with the app's variables too. What still asks per head is whether the code may run here at all (src/core/pull_trust.ts, "Approve to run here"), so a new head from a fork on the origin waits for that approval before anything runs. Approve a guest when you trust its author with the preview's variables, not only its current diff.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs