dependabot: target develop (rebases were resetting the base to master) - #273
Merged
Merged
Conversation
flupkede
added
the
no-changelog
flupkede
pushed a commit
that referenced
this pull request
Sep 17, 2026
This was referenced Sep 17, 2026
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
1 participant
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.
Follow-up on #247. dependabot always opens (and re-rebases) its PRs against the repo's default branch — master here — unless
target-branchis set. Today that surfaced concretely: the nine open dependabot PRs were retargeted to develop, but each@dependabot rebasereset the base straight back to master, re-failing thecheck-source-branchguard.With
target-branch: developon both update blocks, new PRs and rebases land on develop permanently — matching the repo's gitflow (integration branch = develop). Config-only change.