ci: use base repository branch for breaking change detector#22006
Merged
rluvaton merged 1 commit intoapache:mainfrom May 3, 2026
Merged
ci: use base repository branch for breaking change detector#22006rluvaton merged 1 commit intoapache:mainfrom
rluvaton merged 1 commit intoapache:mainfrom
Conversation
this is fixing the issue where forks have stale target branch (stale main)
github-actions
Bot
added
the
development-process
Member
Author
|
@kumarUjjawal can you please review? |
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
2 participants
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.
this is fixing the issue where forks have stale target branch (stale main)
Which issue does this PR close?
Rationale for this change
Making breaking change detector work for stale repositories
What changes are included in this PR?
dont use
originas the remote but use the base repository as the originAre these changes tested?
manually
Are there any user-facing changes?
Nope