5 | | For Macports Pull Requests, it looks like one needs to clone the Macports GitHub repo to a local git repo on their own Mac, make a branch, make changes, commit, rebase etc and then make a Pull Request (PR) from the branch of the local git repo to the Macport Github site. And optionally one can push one's changes from the local git repo to one's personal GitHub.com repo (which was presumably forked or cloned from the Macports GitHub repo earlier). |
| 5 | For Macports Pull Requests, it looks like the following is the best workflow: |
| 6 | |
| 7 | 1. If this has not been done before, fork the Macports GitHub repo (which will create an identical repo on one's personal GitHub website). |
| 8 | |
| 9 | 2. Clone your personal GitHub repo to a local git repo located on their own Mac. |
| 10 | |
| 11 | 3. Using the local git repo, make a branch, makes changes to files in the branch (or add files to the branch), test the port, commit the changes to the local git repo, rebase if needed to reduce the number of commits etc. |
| 12 | |
| 13 | 4. Push one's changes from the local git repo to one's personal GitHub.com repo. |
| 14 | |
| 15 | 5. Make a Pull Request (PR) from the branch of one's personal GitHub repo to the Macports Github site. |