Skip to content

doc: edit "Technical How-To" section of guide #26601

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Trott wants to merge 2 commits into from
Closed

doc: edit "Technical How-To" section of guide #26601

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9721185
doc: edit "Technical How-To" section of guide
Trott Mar 11, 2019
a886e99
Update COLLABORATOR_GUIDE.md
vsemozhetbyt Mar 12, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update COLLABORATOR_GUIDE.md 
Co-Authored-By: Trott <rtrott@gmail.com>
  • Loading branch information
@vsemozhetbyt @Trott
vsemozhetbyt and Trott authored Mar 12, 2019
commit a886e9912b0cf0b5e35673df056cfda3b61a5796
2 changes: 1 addition & 1 deletion COLLABORATOR_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -575,7 +575,7 @@ $ git rev-list upstream/master...HEAD | xargs core-validate-commit
```

Optional: For your own commits, force push the amended commit to the pull
request branch. If your branch name is bugfix, then: `git push
request branch. If your branch name is `bugfix`, then: `git push
--force-with-lease origin master:bugfix`. Don't close the PR. It will close
after you push it upstream. It will have the purple merged status rather than
the red closed status. If you close the PR before GitHub adjusts its status, it
Expand Down