Repository navigation
Speed up CI - #13
Merged
Merged
Speed up CI#13
Conversation
This file contains hidden or 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
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.
What and why
CI takes about two and a half minutes, and part of that is repeated work.
actions/cachekeeps~/.nuget/packagesbetween runs, keyed on the project files andglobal.json, so restore no longer downloads every package each time. A change to a project file misses the exact key, falls back to the newest cache and downloads only what changed.dotnet formatgets--no-restore, since the step before it has just restored.The format check stays whole: the build does not enforce code style (
EnforceCodeStyleInBuildis off), so it still catches what the build would not.Validation
dotnet format --verify-no-changes --no-restorepasses locally.