File tree 1 file changed +8
-8
lines changed
1 file changed +8
-8
lines changed Original file line number Diff line number Diff line change @@ -596,20 +596,20 @@ Validate that the commit message is properly formatted using
596
596
$ git rev-list upstream/master...HEAD | xargs core-validate-commit
597
597
```
598
598
599
+ Optional: When landing your own commits, force push the amended commit to the
600
+ branch you used to open the pull request. If your branch is called ` bugfix ` ,
601
+ then the command would be ` git push --force-with-lease origin master:bugfix ` .
602
+ When the pull request is closed, this will cause the pull request to
603
+ show the purple merged status rather than the red closed status that is
604
+ usually used for pull requests that weren't merged.
605
+
599
606
Time to push it:
600
607
601
608
``` text
602
609
$ git push upstream master
603
610
```
604
- * Optional: Force push the amended commit to the branch you used to
605
- open the pull request. If your branch is called ` bugfix ` , then the
606
- command would be ` git push --force-with-lease origin master:bugfix ` .
607
- When the pull request is closed, this will cause the pull request to
608
- show the purple merged status rather than the red closed status that is
609
- usually used for pull requests that weren't merged. Only do this when
610
- landing your own contributions.
611
611
612
- * Close the pull request with a "Landed in ` <commit hash> ` " comment. If
612
+ Close the pull request with a "Landed in ` <commit hash> ` " comment. If
613
613
your pull request shows the purple merged status then you should still
614
614
add the "Landed in <commit hash >..<commit hash >" comment if you added
615
615
multiple commits.
You can’t perform that action at this time.
0 commit comments