ci: limit update frequency of github/codeql-action #3052
Closed
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
The `github/codeql-action` is released frequently, with each merged PR triggering a new release. This creates a lot of noise in the form of Renovate PRs. To reduce this noise, limit the update checks for this action to twice a week, aligning it with the schedule for other frequently updated packages.
angular-robot
bot
added
the
area: build & ci
alan-agius4
added
action: merge
Member
|
This PR was merged into the repository. The changes were merged into the following branches:
|
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The
github/codeql-actionis released frequently, with each merged PR triggering a new release. This creates a lot of noise in the form of Renovate PRs.To reduce this noise, limit the update checks for this action to twice a week, aligning it with the schedule for other frequently updated packages.