docs: ask contributors to not force-push their branches (#7590)

This commit is contained in:
HonkingGoose 2020-10-28 16:51:34 +01:00 committed by GitHub
parent 7caa7b50ae
commit 5d025236d4
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 9 additions and 0 deletions

View file

@ -23,6 +23,12 @@ afterwards. Also, let the maintainers know that you plan to work on a particular
Pull Requests can only be merged once all status checks are green, which means `yarn test` passes, and coverage is 100%.
## Do not force push to your pull request branch
Please do not force push to your PR's branch after you have created your PR, as doing so makes it harder for us to review your work.
PRs will always be squashed by us when we merge your work.
Commit as many times as you need in your pull request branch.
## Slack collaboration with maintainers
Sometimes the codebase can be a challenge to navigate, especially for a first-time contributor. We don't want you spending an hour trying to work out something that would take us only a minute to explain.

View file

@ -24,3 +24,6 @@ I have verified these changes via:
- [ ] Unit tests + ran on a real repository
<!-- Do you have any suggestions about this PR template? Edit it here: https://github.com/renovatebot/renovate/edit/master/.github/pull_request_template.md -->
<!-- Please do not force push to this PR's branch after you have created this PR, as doing so makes it harder for us to review your work. -->
<!-- PRs will always be squashed by us when we merge your work. Commit as many times as you need in this branch. -->