silverwind c6ca020281 ci: implement gitea's cache-seeder (#1350) ...

Like Gitea's CI, only a `cache-seeder` workflow on main saves the go caches, all other jobs only restore them. Caches are scoped per repository, so until now any pull request, forks included, could write a cache that other runs restore. The seeder compiles the tests without running them, so no test result is ever cached.

Reviewed-on: https://gitea.com/gitea/runner/pulls/1350
Reviewed-by: Lunny Xiao <[email protected]>
Co-authored-by: silverwind <[email protected]>

2026-10-24 17:04:51 +00:00

..

action.yml

ci: implement gitea's cache-seeder (#1350)

2026-10-24 17:04:51 +00:00