Repository navigation
ci: merge Renovate updates without a pull request - #19
Merged
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
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.
Renovate now merges its automerge updates straight into
mainonce the CI of its branch is green (automergeType: branch), instead of opening a pull request. Successful updates no longer request a review from the maintainers, so they no longer send notifications. When the CI fails, Renovate opens a pull request as before.The CI also runs on pushes to
renovate/**, since Renovate waits for the checks of its branch before merging.Needs the Renovate bypass on the
mainruleset from tf-github first.