@@ -154,7 +154,7 @@ When you fork a project in order to propose changes to the original repository,
|
||||
|
||||
6. Type `git remote add upstream`, and then paste the URL you copied in Step 3 and press **Enter**. It will look like this:
|
||||
```shell
|
||||
$ git remote add upstream https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/Spoon-Knife.git
|
||||
$ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git
|
||||
```
|
||||
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
|
||||
|
||||
@@ -50,14 +50,14 @@ When installing or publishing a Docker image, the {% data variables.product.prod
|
||||
|
||||
## Pushing container images
|
||||
|
||||
This example pushes the latest version of `IMAGE-NAME`.
|
||||
This example pushes the latest version of `IMAGE_NAME`.
|
||||
```shell
|
||||
$ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:latest
|
||||
```
|
||||
|
||||
This example pushes the `2.5` version of the image.
|
||||
```shell
|
||||
$ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE-NAME:2.5
|
||||
$ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:2.5
|
||||
```
|
||||
|
||||
When you first publish a package, the default visibility is private. To change the visibility or set access permissions, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
|
||||
|
||||
Reference in New Issue
Block a user