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.

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

Improved CI - check fmt #156

Merged
merged 2 commits into from
Sep 13, 2024

Conversation

alfonsorr
Copy link
Collaborator

Changed the scala setup plugin to a maintained action. Pipeline to check if the format is correct.
Added a cache to improve the speed in CI runs.
Updated checkout action to the latest version.

@alfonsorr alfonsorr requested a review from zeotuan September 11, 2024 14:10
@alfonsorr alfonsorr force-pushed the feature/validate-scalafmt branch 3 times, most recently from 0761e35 to 934d1fe Compare September 11, 2024 14:30
@alfonsorr
Copy link
Collaborator Author

@SemyonSinchenko @zeotuan I'm thinking of moving the benchmarking to the CI quality pipeline to run it only once and in parallel to speed up testing.

Changed the scala setup plugin to a maintained action.
Pipeline to check if the format is correct.
Added a cache to improve the speed in CI runs.
Updated checkout action to the latest version.
@alfonsorr alfonsorr force-pushed the feature/validate-scalafmt branch from ebcd845 to e64eca8 Compare September 12, 2024 09:54
Copy link
Collaborator

@zeotuan zeotuan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@alfonsorr alfonsorr merged commit 0f5e839 into mrpowers-io:main Sep 13, 2024
6 checks passed
@alfonsorr alfonsorr deleted the feature/validate-scalafmt branch September 13, 2024 08:37
@zeotuan
Copy link
Collaborator

zeotuan commented Sep 16, 2024

@SemyonSinchenko @zeotuan I'm thinking of moving the benchmarking to the CI quality pipeline to run it only once and in parallel to speed up testing.

Sound good! Do you think we should still have benchmarks running for different version?

@alfonsorr
Copy link
Collaborator Author

Maybe have it for only one in the pr's or when merged and maybe in the release flow test against all of them. Not sure if testing against multiple versions will make a difference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants