Repository navigation
ci: rebase Renovate pull requests when they are behind master - #81
Merged
Merged
Conversation
Renovate PRs opened before the pull_request workflow have no run. With rebaseWhen behind-base-branch, Renovate rebases them onto master, and the workflow runs on the new head. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Summary
This change adds
renovate.jsonwithrebaseWhen: behind-base-branch.The repository has no Renovate configuration file on
master. Renovate uses its default: it rebases a pull request only when the pull request has a conflict, or when a person ticks the rebase box in the pull request body. The six Renovate pull requests #48, #49, #51, #53, #55 and #56 have no conflict, so they stay on an oldmaster.With this setting, Renovate rebases each pull request that is behind
masteron its next run, under its own identity. No person edits a bot body.What does not change
extends, schedule, automerge or package rule. There is no org preset (OpenVoiceOS/renovate-configdoes not exist), so the other Renovate defaults stay as they are.validate_raw_jsons.ymlon the six pull requests. That workflow has apathsfilter (raw_jsons/**, two scripts, the workflow file), and the six pull requests change onlyfrontend/package-lock.json. A workflow that runs onfrontend/**is separate work.Check after merge
On the next Renovate run, the six pull requests get a new head on
master.git merge-base --is-ancestor origin/master <head>returns 0 for each.AI-authorship disclosure: an AI agent (Claude) wrote this change and this description.
🤖 Generated with Claude Code