Push to a fork. A new branch pushed to a fork prints the address that opens its pull into the fork's upstream. git push -o pull origin <branch> opens it (title and body from the tip commit's message); a later push to that branch prints the open pull's address.
Landing. Each repository has a setting, How a pull lands (landing in the API's repository settings): merge (default, a merge commit for a kept fork's pull) or linear (opt-in). Linear: a one-commit pull on an unmoved base whose author is a real address and whose subject has no pull number fast-forwards; any other lands as one commit on the base, authored by the contributor, titled <title> (#<upstream number>) with any (#n) from the contributor's own forge dropped. Existing repositories keep merge.
Approval. A force-push that only rebases a pull onto a moved base (the same change, line for line) keeps its approvals; any other change makes them stale as before (src/core/carry_approval.ts).
Not done: a non-member pushing to the upstream still hears "repository not found"; rebase as a third way to land.