Login to ghcr.io using GITHUB_TOKEN (#3983)
I am hoping this change will fix the problem with the "develop" workflow: denied: permission_denied: write_package We will see when we merge this PR. It works automatically without a need to create a Personal Access Token, which means It also works auomatically on any forked repos, our personal repos. GITHUB_TOKEN has a limited lifespan unlike a PAT so it more secure too and the recommended way to do this now at github.
This commit is contained in:
parent
dd70d9a18c
commit
40fdbbcc39
1 changed files with 2 additions and 5 deletions
7
.github/workflows/develop.yml
vendored
7
.github/workflows/develop.yml
vendored
|
@ -4,6 +4,7 @@ on:
|
|||
push:
|
||||
branches:
|
||||
- develop
|
||||
|
||||
jobs:
|
||||
linux_job:
|
||||
runs-on: ubuntu-20.04
|
||||
|
@ -14,11 +15,7 @@ jobs:
|
|||
- name: Fetch Deps
|
||||
run: ci/actions/linux/install_deps.sh
|
||||
- name: Login to ghcr.io
|
||||
uses: docker/login-action@adb73476b6e06caddec5db0bc1deacbec8cdd947
|
||||
with:
|
||||
registry: ghcr.io
|
||||
username: ${{ github.repository_owner }}
|
||||
password: ${{ secrets.GHCR_PAT }}
|
||||
run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u $ --password-stdin
|
||||
- name: Deploy Docker (ghcr.io)
|
||||
run: ci/actions/linux/ghcr_push.sh
|
||||
- name: Deploy Docker (nanocurrency/nano-env)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue