zotac/graylog-deploy
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

CI: authenticate the deploy clone so it keeps working once the repo is private

Browse source 
Forgejo auto-issues a per-job, repo-scoped secrets.GITHUB_TOKEN (created at
workflow start, destroyed at completion, usable only against this repo);
use it in the clone URL instead of an anonymous HTTPS clone, which would
start failing with 401/403 the moment the repo's visibility changes.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
byrsapty 2026-07-22 21:42:36 +03:00
parent 0da7aa5a14
commit 3e46b08db5
1 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
.forgejo/workflows/deploy.yml
View file

@ -15,9 +15,13 @@ jobs:
GRAYLOG_EXTERNAL_URI: http://93.171.241.5:9000/
GRAYLOG_ADMIN_PASSWORD: ${{ secrets.GRAYLOG_ADMIN_PASSWORD }}
DISCORD_WEBHOOK_URL: ${{ secrets.DISCORD_WEBHOOK_URL }}
# Forgejo issues this automatically per-job, scoped to this repo only -
# needed once the repo is private, since a plain anonymous clone would
# get 401/403. No extra secret to manage: it's provided by the platform.
CI_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
rm -rf /tmp/graylog-deploy-ci
git clone --depth 1 --branch main https://git.zotac.keenetic.link/zotac/graylog-deploy.git /tmp/graylog-deploy-ci
git clone --depth 1 --branch main "https://x-access-token:${CI_TOKEN}@git.zotac.keenetic.link/zotac/graylog-deploy.git" /tmp/graylog-deploy-ci
cd /tmp/graylog-deploy-ci
chmod +x install-graylog.sh
./install-graylog.sh