ci: reduce the steady stream of dependabot PRs #138
Merged
Conversation
This file contains 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
PR intel#107 introduced dependabot to the repository to update GitHub Actions. This results in a weekly stream of PRs to incorporate every tiny patch update for every GitHub Action we use here. This results in a lot of churn and I do not have any sense that it improves the code quality in any way. Instead, it may in fact be the cause of the breakage in the release workflow, since that relies on `upload-artifact` which dependabot bumped from v3.1.3 to v4.0.0. What this change does is follow GitHub's [guidance] to only receive security updates. Since "dependabot security updates" are enabled, we don't need to follow each action update; setting `open-pull-requests-limit` to 0 mutes the dependabot PRs but we should still see any security alerts in the security tab. [guidance]: https://docs.github.com/en/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#overriding-the-default-behavior-with-a-configuration-file
|
Other options:
cc: @rahulchaphalkar |
|
Thanks for bringing this up, the weekly updates on GitHub actions are definitely not needed. I know we discussed changing the frequency to monthly and/or ignoring certain types of updates, but even just changing the PRs to 0 as you have done should be enough. |
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.
PR #107 introduced dependabot to the repository to update GitHub Actions. This results in a weekly stream of PRs to incorporate every tiny patch update for every GitHub Action we use here. This results in a lot of churn and I do not have any sense that it improves the code quality in any way. Instead, it may in fact be the cause of the breakage in the release workflow, since that relies on
upload-artifactwhich dependabot bumped from v3.1.3 to v4.0.0 (see #126).What this change does is follow GitHub's guidance to only receive security updates. Since "dependabot security updates" are enabled, we don't need to follow each action update; setting
open-pull-requests-limitto 0 mutes the dependabot PRs but we should still see any security alerts in the security tab.