...
To start, make sure you have the latest commits from the upstream codebase’s default branch (which is usually the master mainbranch). Then create a new topic or feature branch for the work you’ll be doing. In practice, it doesn’t much matter what you name this branch – some name it based on a brief description of the changes they will be making, and some include the issue number, but neither of these are ever included in the code review process. Do not work directly on the master main branch, which is a protected branch.
...
Next, you’ll want to check that your branch is up to date with its parent branch (likely to be master main); if you kept your PR small and targeted, you will find that this isn’t a difficult process. Make sure your code conforms to style guidelines and your test suite is green, and then push your branch and create a pull request.