Discussion about PR contribution best practices
See original GitHub issueSome new best practices were introduced into https://github.com/corona-warn-app/cwa-website/blob/master/CONTRIBUTING.md#pull-request-checklist recently (see below).
I’d like to start this thread as an open discussion to help collaboration and implementing the best practices.
Pull Request Checklist
-
Use a git GUI interface if you are new to
git
. It will help you getting familiar with the basic submission workflow. -
Branch from the
master
branch and also targetmaster
with your Pull Request. -
Commits should be as small as possible while ensuring that each commit is correct independently (i.e., each commit should compile and pass tests).
-
Create Draft pull requests only if you need clarification or an explicit review before you can continue your work item.
-
If your patch is not getting reviewed or you need a specific person to review it, you can @-reply a reviewer asking for a review in the pull request or a comment, or you can ask for a review by contacting us via email.
-
Post review:
- Integrate the requested changes into your submission.
- Set respective comments in your GitHub review to resolved.
- Rebase your PR to the latest upstream
master
branch. - Create a general PR comment to notify the reviewers that your amendments are ready for another round of review.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:9 (9 by maintainers)
Top GitHub Comments
@MikeMcC399 sorry for not following best practices, I’m still learning and will give my best to follow them from now on. I’m not a member of the Open Source Team, I get my information from other people who then assign tasks to me.
After merging the master branch into a open PR, pulling it locally then adding a commit, GitHub Desktop wouldn’t let me squash. I had to rebase on master then I could squash and force push to origin. Still learning here 🙂 !