[TT-1929] make sure go.mods are tidy #1541
Merged
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.
Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.
Why
The changes implement new jobs and steps in the GitHub Actions workflow to enhance code quality and dependency management. Specifically, they add a job for cleaning Go modules, ensuring all dependencies are correctly managed and tidy. This is crucial for maintaining a clean and efficient codebase.
What
clean-go-mods
to run Go modules cleanup. This includes setting up Go 1.23.3, installing gomods, checking out code, runninggomods tidy
, and ensuring the codebase is clean after the tidy operation. This ensures that the project's dependencies are properly managed and free from unnecessary modules.pre-commit
,tools
,golangci
,vulnerabilities-check
,asdf-install
,helmlint
,actionlint
, andsonarqube
remain unchanged, focusing on their specific tasks like linting, vulnerabilities check, installing dependencies, linting Helm charts, validating GitHub Action workflows, and running SonarQube analysis respectively.