Skip to content

feat(vcs): Prefer upstream remote over origin for base repo name#2737

Merged
runningcode merged 2 commits intomasterfrom
no/prefer-upstream-remote
Sep 12, 2025
Merged

feat(vcs): Prefer upstream remote over origin for base repo name#2737
runningcode merged 2 commits intomasterfrom
no/prefer-upstream-remote

Conversation

@runningcode
Copy link
Copy Markdown
Contributor

Summary

Prefer "upstream" remote over "origin" when determining base repository name, following Git fork conventions.

🤖 Generated with Claude Code

Copy link
Copy Markdown
Member

@szokeasaurusrex szokeasaurusrex left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah approved too early – please adjust the function's doc comment to reflect the new behavior 🙏

Then, this looks good!

@runningcode
Copy link
Copy Markdown
Contributor Author

Updated

runningcode and others added 2 commits September 12, 2025 09:16
When determining the base repository name, now prioritizes:
1. upstream (if exists)
2. origin (if exists)
3. first available remote

This follows Git conventions where upstream typically refers to the
original repository when working with forks.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
…preference

Update function documentation to correctly reflect that we now prefer
"upstream" remote first, then "origin", then first available remote.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@runningcode runningcode merged commit 775f60f into master Sep 12, 2025
23 checks passed
@runningcode runningcode deleted the no/prefer-upstream-remote branch September 12, 2025 09:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants