Files
endorphin-tessera-gui/.gitea/README.md
T
codex-bot 3e1cce78f8
Verify Tessera GUI / verify (push) Successful in 9m54s
fix: use standard CI checkout with package-only Aster
2026-10-20 02:39:47 +08:00

27 lines
1.3 KiB
Markdown

# Tessera GUI automation
[workflows](workflows/README.md) contains repository workflows.
## CI source checkout
All workflows use `runs-on: ces-control`; no shared Runner configuration is changed.
`actions/checkout@v4` reads source over HTTPS using Gitea's automatically supplied
`GITEA_TOKEN`. No additional SSH key or known_hosts secrets are required, and
`persist-credentials: false` prevents credentials from being retained for later
build steps.
Consumer workflows read the exact Aster commit from the checked-out project's
`vendor/aster` gitlink, then use another standard checkout into that directory and
verify the resulting HEAD. They do not follow Aster main automatically. Aster is
currently a public repository, so reading it does not require private cross-repo
authorization. If that visibility changes, diagnose the job token's read access
instead of assuming an SSH key must be distributed.
The SSH URL in `.gitmodules` is retained for developer Git operations, which
continue to use the dedicated codex-bot identity. CI's built-in job token is
separate from local developer credentials.
Workflow definitions do not prove CI passed. CI/deployment state is not queried
automatically. Local runtime checks are not performed for Aster, Lyra or Hestia;
Tessera permits local native builds/window runs, with automated tests in CI.