Fix Git::remoteName() to prefer origin remote#155
Closed
jonathonbyrdziak wants to merge 1 commit intomasterfrom
Closed
Fix Git::remoteName() to prefer origin remote#155jonathonbyrdziak wants to merge 1 commit intomasterfrom
jonathonbyrdziak wants to merge 1 commit intomasterfrom
Conversation
Repos with multiple remotes (e.g. origin + launchpad) would use whichever remote appeared first alphabetically, causing releases to push to the wrong remote. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
Author
|
Already fixed on master — duplicate |
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
Git::remoteName()now returnsoriginwhen it exists, instead of the first remote alphabeticallylaunchpadinstead oforigin) in repos with multiple remotesTest plan
protocol release:createpushes tooriginin repos with multiple remotes🤖 Generated with Claude Code