From: Joana Pires, maintainer, Fernhill garden-monorepo
"Thanks for spotting the wrong delivery promise in packages/delivery/notes.md. Please send the fix as a pull request from your fork, rebased on our latest main: we merged a billing change this morning.
Customers on 1.4 see the same text, so once it's reviewed, please also backport just that commit to release-1.4, tag it v1.4.1 and push the release branch. Don't bring the billing change into 1.4: it isn't released yet."
Done looks like: a rebased, pushed topic branch with an open pull request, and a release-1.4 branch with only the fix added, tagged v1.4.1 and pushed to your fork.
Open-source projects and many companies work this way: you can't push to the main project, so you push to your own fork and propose changes from there. This project follows one fix all the way, in a monorepo that holds several packages.
You will branch from your fork, change one file inside the delivery package and leave a scratch note out of the commit, bring in the project's newer work by rebasing onto upstream/main, push to your fork with an upstream branch set, and open a pull request. Then the maintainers ask for the fix in the current release: you cherry-pick only that commit onto release-1.4, without the unreleased changes from main, tag the patch release and publish the release branch.
In this repository, origin is your fork and upstream is the project; both are simulated servers in your browser. Your repository carries from step to step.
origin is your fork; upstream is the project you contribute to.