Taking updates from an origin you follow

A repository that follows an upstream address (a connected origin, a migration, a pasted link; repo_upstream) takes its updates the way a fork takes its parent's. The doors ask for a parent in this forge first and come to src/actions/upstream_sync.ts when there is none.

Where

A check moves main too

While following is on, every check of the upstream (the clock's, or Check upstream now) settles the default branch before it reads what is behind, with nobody pressing Take:

Each move is a push event carrying followed, so what follows a push follows it. Anything else (a branch with work the upstream lacks) is left for Take, a proposal or the crew.

Taking stages the upstream tip in the bare repository (no clone), writes a push event carrying followed, and needs write access.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs