Sync your fork/branch before making a pull-request

[mikhael28]

I wanted to make a quick public service announcement. There are really only two rules when it comes to pull-requests that I think are super relevant towards getting an open-source project really rolling.

1. Never send a pull-request with code that is either broken, or that you have not manually tested/verified is NOT broken. If I find an edge case, that's okay - but I shouldn't open up a component and immediately have it break.
2. Before sending in a pull-request, always pull (merge) the latest code from the upstream (read: mikhael28/paretOS) repository into YOUR forked repository branch. This way, your branch has the latest code from main, so that before you send a pull-request, you can check to make sure if any newly merged code overrides/supersedes the code you've written. Your code-base could be super duper behind, aka outdated.

Refer to this link for details, scroll down to see the command line keys: https://docs.github.com/en/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

p.s. after you sync your fork, you still need to PUSH your changes to your GitHub repository, to then send a pull-request to the upstream repository.