jdevega/deployment-policies
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ci: use DEPLOY_TOKEN secret (GITEA_ prefix is reserved)
ci / verify (push) Successful in 4m3s
Details
ci / publish (push) Failing after 47s
Details

Browse Source 
Gitea forbids secret names starting with GITEA_; map the DEPLOY_TOKEN
secret to the GITEA_TOKEN env var consumed by publish.sh.
This commit is contained in:
jdevega
2026-09-15 20:34:56 +02:00
parent cc8e9a23b3
commit 953523e40a
5 changed files with 13 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+6 -2
View File
@@ -127,6 +127,9 @@ make publish # upload all bundles to the Gitea generic registry
- `GITEA_URL` (default `https://gitea.devegamoreno.com`)
- `GITEA_OWNER` (default `jdevega`)
In CI, set a secret named `DEPLOY_TOKEN` on the repository — the secret name must not start with
the reserved `GITEA_` prefix — and `publish.sh` exposes it to the job as `GITEA_TOKEN`.
Artifacts land at:
```
@@ -147,9 +150,10 @@ generated changeset. Later run `make version` to apply them. See
`.gitea/workflows/ci.yml`:
1. `verify` — `npm ci`, install OPA, `scripts/check.sh`, `scripts/build.sh` (every push/PR).
2. `publish` — on `main` only, rebuilds and uploads bundles with `GITEA_TOKEN`.
2. `publish` — on `main` only, rebuilds and uploads bundles with the `DEPLOY_TOKEN` secret.
Create the `GITEA_TOKEN` repository secret on Gitea with at least `write:package` scope.
Create the `DEPLOY_TOKEN` repository secret on Gitea with at least `write:package` scope
(secret names cannot start with `GITEA_`).
## Evaluating a bundle