Skip to content

Commit 1dbecb0

Browse files
committed
Github -> GitHub
1 parent e8a6a76 commit 1dbecb0

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

docs/build/how-to/build-and-deploy.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@
22
tags: [build, deploy, how-to]
33
---
44

5-
# Build and deploy with Github Actions
5+
# Build and deploy with GitHub Actions
66

7-
This how-to guide shows you how to build and deploy your application using [Github Actions](https://help.github.com/en/actions/automating-your-workflow-with-github-actions) and the Nais deploy action.
7+
This how-to guide shows you how to build and deploy your application using [GitHub Actions](https://help.github.com/en/actions/automating-your-workflow-with-github-actions) and the Nais deploy action.
88

99
## Prerequisites
1010

@@ -64,7 +64,7 @@ When this file is pushed to the `main` branch, the workflow will be triggered an
6464
!!! info "Registry used by Nais"
6565

6666
The [nais/docker-build-push GitHub action](https://github.com/nais/docker-build-push) as well as the
67-
[nais/login GitHub action](https://github.com/nais/login) works with a registry that is only meant for use within the Nais platform.
67+
[nais/login GitHub action](https://github.com/nais/login) work with a registry that is only meant for use within the Nais platform.
6868

6969
Usage of this registry for other purposes is not supported.
7070
If you need to use the image outside of Nais, e.g. locally in a development environment, you should [push the image to another registry](./use-image-outside-nais.md).

docs/build/how-to/use-image-outside-nais.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ tags: [how-to, build, image]
77
When using the [nais/docker-build-push](https://github.com/nais/docker-build-push) action, the image is pushed to a registry that is meant for use within the Nais platform.
88
If you need to use the image outside of Nais, e.g. locally in a development environment, you should push the image to another registry.
99

10-
## Push to Github Container Registry
10+
## Push to GitHub Container Registry
1111

12-
After the image is built by `nais/docker-build-push`, you can push it to the Github Container Registry (GHCR) by adding the following step to your workflow:
12+
After the image is built by `nais/docker-build-push`, you can push it to the GitHub Container Registry (GHCR) by adding the following step to your workflow:
1313

1414
- `packages: write` permission is required to push images to the GHCR.
1515
- Step to retag the image after it has been built.
@@ -37,7 +37,7 @@ jobs:
3737
team: <MY-TEAM> # Replace
3838
- name: Push image to ghcr.io
3939
run: |
40-
# Log in to the Github Container Registry
40+
# Log in to the GitHub Container Registry
4141
echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin
4242
# Tag the image, e.g. ghcr.io/owner/repo:latest
4343
docker buildx imagetools create -t ghcr.io/${{ github.repository }}:latest ${{ steps.docker-build-push.outputs.image }}

0 commit comments

Comments
 (0)