...
You will have a local repo with two remotes: “origin” will point to your fork in your account, and “upstream” will point to the repo in the openedx org. The normal flow will be:
Pull from upstream the upstream’s master branch into your fork’s master branch to get the latest code.
Make a feature branch in your repo from your repo’s master branch. Don’t work directly
Make your changes, and commit them.
Push your branch to your fork (origin).
Make a pull request against upstream.
Once the review is complete, the owning team will approve and merge the pull request.
...
Visit the repo on GitHub.
In the upper-right corner is a Fork button. Click it.:
On the next screen, you will be asked where to fork it, called the Owner. Choose your own personal account (the default choice).:
edx will be listed in the drop-down, with “insufficient permission”
DO NOT FORK INTO edx EVEN IF YOU CAN. Use your personal account.
...
How you get the fork locally depends on whether you already have a local repo copy that you want to keep. If you have a local copy but don’t need it, you can delete the repo directory and use “I don’t have a local copy.”
A. I don’t have a local copy
Clone the repo locally:
git clone https://github.com/USER/REPO.gitAdd a new remote for upstream:
git remote add upstream https://github.com/openedx/REPO.git
B. I have a local copy I want to keep
Rename the existing remote:
Use
git remote -vto check that the openedx repo is named “origin”Rename the remote to “upstream”:
git remote rename origin upstream.
Add a new remote for your fork:
git remote add origin https://github.com/USER/REPO.git
B. I don’t have a local copy
Clone the repo locally:
git clone https://github.com/USER/REPO.gitAdd a new remote for upstream:git remote add upstream https://github.com/openedx/REPO.git
Keeping your fork up to date
You now have two remote repos (your fork and the openedx core repo) that you might need to get changes from.
...