fix: Use SECRET instead of GITEA_TOKEN (Gitea naming restriction)
This commit is contained in:
parent
af0f8e1f7a
commit
e8ef0710a2
@ -187,7 +187,7 @@ jobs:
|
|||||||
|
|
||||||
- name: Deploy to CT109
|
- name: Deploy to CT109
|
||||||
run: |
|
run: |
|
||||||
export GITEA_TOKEN="${{ secrets.GITEA_TOKEN }}"
|
export GITEA_TOKEN="${{ secrets.SECRET }}"
|
||||||
ssh -i ~/.ssh/deploy_key -p ${{ secrets.CT109_SSH_PORT }} ${{ secrets.CT109_USER }}@${{ secrets.CT109_HOST }} bash -s << ENDSSH
|
ssh -i ~/.ssh/deploy_key -p ${{ secrets.CT109_SSH_PORT }} ${{ secrets.CT109_USER }}@${{ secrets.CT109_HOST }} bash -s << ENDSSH
|
||||||
set -e
|
set -e
|
||||||
export VERSION="${{ github.sha }}"
|
export VERSION="${{ github.sha }}"
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user