Skip to content

Commit 83129b5

Browse files
authored
Merge pull request github#15286 from cloudcosmonaut/patch-2
Force pushing has its use
2 parents 3958ff8 + 06f56b7 commit 83129b5

File tree

1 file changed

+1
-1
lines changed
  • content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests

1 file changed

+1
-1
lines changed

content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ topics:
2121

2222
**Note:** When working with pull requests, keep the following in mind:
2323
* If you're working in the [shared repository model](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models), we recommend that you use a topic branch for your pull request. While you can send pull requests from any branch or commit, with a topic branch you can push follow-up commits if you need to update your proposed changes.
24-
* When pushing commits to a pull request, don't force push. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on.
24+
* Be very careful when force pushing commits to a pull request. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on.
2525

2626
{% endnote %}
2727

0 commit comments

Comments
 (0)