sylvain/test
1
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages 1 Wiki Activity Actions

ci: cache mise tools and Go build artifacts in Forgejo pipelines #2

Merged
sylvain merged 1 commit from chore/cache-mise-go-ci into main 2026-06-02 05:58:36 +02:00
Conversation 0 Commits 1 Files changed 2 +61
sylvain commented 2026-06-02 05:58:31 +02:00
Owner
Copy link

Each mise job re-bootstrapped the full toolchain (go, golangci-lint,
task, goreleaser) and recompiled the module from scratch on every run.
Add actions/cache@v4 steps for mise's data/cache dirs (keyed on
mise.toml) and the Go module/build caches (keyed on go.sum) so repeat
runs restore instead of re-downloading and recompiling.

actions/cache is used over jdx/mise-action because the latter is not
mirrored on Forgejo's default actions registry, while actions/cache is
(resolves the same way as the existing actions/checkout@v4). The bootstrap
flow is unchanged; on a cache hit mise install becomes a near no-op.

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

Each mise job re-bootstrapped the full toolchain (go, golangci-lint, task, goreleaser) and recompiled the module from scratch on every run. Add actions/cache@v4 steps for mise's data/cache dirs (keyed on mise.toml) and the Go module/build caches (keyed on go.sum) so repeat runs restore instead of re-downloading and recompiling. actions/cache is used over jdx/mise-action because the latter is not mirrored on Forgejo's default actions registry, while actions/cache is (resolves the same way as the existing actions/checkout@v4). The bootstrap flow is unchanged; on a cache hit `mise install` becomes a near no-op. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ci: cache mise tools and Go build artifacts in Forgejo pipelines
All checks were successful
/ test (push) Successful in 1s
Details
snapshot / linters (push) Successful in 1m34s
Details
snapshot / goreleaser-snapshot (push) Successful in 33s
Details
snapshot / linters (pull_request) Successful in 14s
Details
snapshot / goreleaser-snapshot (pull_request) Successful in 33s
Details
aaa8c6d7a2 
Each mise job re-bootstrapped the full toolchain (go, golangci-lint,
task, goreleaser) and recompiled the module from scratch on every run.
Add actions/cache@v4 steps for mise's data/cache dirs (keyed on
mise.toml) and the Go module/build caches (keyed on go.sum) so repeat
runs restore instead of re-downloading and recompiling.

actions/cache is used over jdx/mise-action because the latter is not
mirrored on Forgejo's default actions registry, while actions/cache is
(resolves the same way as the existing actions/checkout@v4). The bootstrap
flow is unchanged; on a cache hit `mise install` becomes a near no-op.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sylvain/test!2
No description provided.