chore(ci): consolidate linters #139
Merged
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
ARR4N
requested review from
a team,
ceyonur,
darioush and
qdm12
and removed request for
a team
ARR4N
added a commit
that referenced
this pull request
Feb 14, 2025
## Why this should be merged New jobs are easily forgotten in the GitHub rules so we will only gate on `go` and have all others added as dependencies. ## How this works Same as #139 ## How this was tested Inspection of CI run: 
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Why this should be merged
Branch-protection rules only require the Go linter (erroneously called
lint) by mistake. All linters are now dependencies of a singlelintjob that remains as a PR gate. New linters will now be enforced by default.Closes #138
How this works
GitHub Actions
needconfiguration. The path limitation of runningyamllintis removed because it's such a cheap job so is ok to always run.How this was tested
Inspection of CI run and PR's required jobs: