Repository navigation
Group Dependabot updates into one monthly PR - #82
Merged
Merged
Conversation
🤖 Generated with Claude Code
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
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.
Dependabot opened one PR per dependency bump, each causing notifications.
It now opens one PR per month for all Composer and GitHub Actions updates, which the existing auto-merge workflow merges.
Renovate branch automerge would avoid PRs entirely, but needs an org owner to install the app
webonyx/graphql-php#1981 uses that approach.
Dependabot cannot merge without a PR.
multi-ecosystem-groups puts Composer and Actions in the same PR
https://docs.github.com/en/code-security/dependabot/working-with-dependabot/configuring-multi-ecosystem-updates
🤖 Generated with Claude Code