You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,10 +42,10 @@ If the changes from the upstream repository cause conflicts, {% data variables.p
42
42
43
43
{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[AUTOTITLE](/github-cli/github-cli/about-github-cli)."
44
44
45
-
To update the remote fork from its parent, use the `gh repo sync -b BRANCHNAME` subcommand and supply your fork and branch name as arguments.
45
+
To update the remote fork from its parent, use the `gh repo sync -b BRANCH-NAME` subcommand and supply your fork and branch name as arguments.
46
46
47
47
```shell
48
-
gh repo sync owner/cli-fork -b BRANCH_NAME
48
+
gh repo sync owner/cli-fork -b BRANCH-NAME
49
49
```
50
50
51
51
If the changes from the upstream repository cause conflict then the {% data variables.product.prodname_cli %} can't sync. You can set the `--force` flag to overwrite the destination branch.
@@ -56,15 +56,15 @@ Before you can sync your fork with an upstream repository, you must configure a
56
56
57
57
{% data reusables.command_line.open_the_multi_os_terminal %}
58
58
1. Change the current working directory to your local project.
59
-
1. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`.
59
+
1. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCH-NAME` will be stored in the local branch `upstream/BRANCH-NAME`.
0 commit comments