chore(deps): aim dependabot at development - #800
Merged
Conversation
Dependabot reads its config from the DEFAULT branch (main here), whose copy carried no target-branch - so every PR was opened against main where branch-protection rejects it. This is development's file verbatim.
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.
Dependabot reads its config from the repository's default branch, which is
mainhere.main'sdependabot.ymlcarries notarget-branch, so every dependabot PR was opened againstmain— wherebranch-protection / check-branchcorrectly rejects it. 1 open PRs in this repo could never merge as a result.This is
development's file verbatim — verified byte-identical by git blob SHA — so it is a forward-port of content already reviewed there, not a new divergence.Existing
main-targeted PRs are being closed so dependabot reopens them againstdevelopment, where they can flow through the normal update channel.