Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Refactor module caching in GitHub Actions workflows #7342

Open
cPu1 opened this issue Nov 29, 2023 · 2 comments
Open

Refactor module caching in GitHub Actions workflows #7342

cPu1 opened this issue Nov 29, 2023 · 2 comments
Assignees
@cPu1
Labels
area/ci kind/improvement priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases

Comments

@cPu1
Copy link
Collaborator

cPu1 commented Nov 29, 2023

Most workflows are currently using actions/setup-go to set up a Go environment and actions/cache to cache and restore Go modules. actions/setup-go, however, has built-in support for module caching and is enabled by default. This can be leveraged to remove usage of actions/cache but care must be exercised to ensure the module cache is built with a consistent key.
@cPu1 cPu1 mentioned this issue Dec 7, 2023
Merged
7 tasks
@cPu1 cPu1 self-assigned this Dec 7, 2023
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Jan 7, 2024

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale label Jan 7, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 13, 2024
@cPu1 cPu1 reopened this Apr 22, 2024
@cPu1 cPu1 added priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases and removed stale labels Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cPu1 cPu1

Labels
area/ci kind/improvement priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cPu1