fix(ci): image tag was empty on scheduled runs (#2)

Co-authored-by: claude <[email protected]>
This commit was merged in pull request #2.
This commit is contained in:
2026-09-01 11:19:09 -04:00
committed by claude
parent 23c7a3d524
commit 0f296a0ec4
3 changed files with 38 additions and 8 deletions
+6 -2
View File
@@ -146,8 +146,12 @@ identifiers that the LLM reads.
You do NOT need to edit the IMAGE env or the `--package` arg in the
workflows. Both derive from the repo at runtime via
`${{ github.repository_owner }}` and
`${{ github.event.repository.name }}`. So a clone into a repo named
`${{ github.repository }}` and `${GITHUB_REPOSITORY##*/}`. Do **not**
use `${{ github.event.repository.name }}` — it resolves to EMPTY on
`schedule` events (Gitea >= 1.27), which silently builds the tag
`<registry>/<owner>/:latest` and fails the build *after* the full
scrape; the `Verify image name resolves` step guards it. So a clone
into a repo named
`my-product-docs` automatically pushes the container as
`<owner>/my-product-docs:latest` and links the package to its own
repo. (`github.*` is Gitea Actions' inherited GitHub-Actions