Lines Matching full:pr

54    label to the PR.
87   gh pr create
110 If you do this, you must squash and merge before landing the PR and
133 After your PR is reviewed and accepted, you want to rebase your branch to ensure
134 you won't encounter merge conflicts when landing the PR.
137   This guide assumes that the PR branch only has 1 author. If you are
144 Before merging a PR you must have the required approvals. See
150 When your PR has been approved you can merge your changes.
157 If the PR is a single commit, all you need to do is click the merge button in
160 If your PR contains multiple commits, you need to consolidate those commits into
181     gh pr merge --squash --delete-branch
208     gh pr merge --squash --delete-branch
243 Even though your PR passed the pre-commit checks and is approved by reviewers, it
248 :ref:`here <MyFirstTypoFix Issues After Landing Your PR>`.
251 Checking out another PR locally
253 Sometimes you want to review another person's PR on your local machine to run
259   gh pr checkout <PR Number>
291   # Create the PR, select to use your own fork when prompted.
293   gh pr create
315 Before merging the PR, it is recommended that you rebase locally and re-run test
333   gh pr merge --squash --delete-branch
344 Instead of using the GitHub CLI to create a PR, you can push your code to a
345 remote branch on your fork and create the PR to upstream using the GitHub web
348 Here is an example of making a PR using git and the GitHub web interface:
410 Before merging the PR, it is recommended that you rebase locally and re-run test
427 Once your PR is approved, rebased, and tests are passing, click `Squash and
428 Merge` on your PR in the GitHub web interface.