chore: Trigger builds on changes in setup-go/action.yml #4098
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
KapJI
force-pushed
the
windows-image
branch
10 times, most recently
from
6bee848
to
3a1d0a5
Compare
KapJI
force-pushed
the
windows-image
branch
2 times, most recently
from
98be728
to
5593c61
Compare
KapJI
changed the title
|
Thank you for all your work here. Sometimes computers are frustrating. This PR still makes chezmoi's CI more accurate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My goal in this PR was figure out why Windows builds are slow (~90s) on the latest image (
20241125.1.0) of github runners when they were much faster (~10s) on previous image version. Unfortunately, I haven't found a solution.RUNNER_TOOL_CACHE) but there is no easy way to always download it. So I was unable to verify if something is wrong with version in the tool cache.