Skip to content

Conversation

@miss-islington
Copy link
Contributor

  • find defined "(fetch)" remotes with "python/cpython" in their URL
  • if there is exactly one, use that remote name
  • if there is one named "upstream", "origin", or "python",
    use that remote (in that precedence order)
  • otherwise report an error listing the defined remotes
    (cherry picked from commit ac9d37c)

Co-authored-by: Kattni [email protected]

* find defined "(fetch)" remotes with "python/cpython" in their URL
* if there is exactly one, use that remote name
* if there is one named "upstream", "origin", or "python",
  use that remote (in that precedence order)
* otherwise report an error listing the defined remotes
(cherry picked from commit ac9d37c)

Co-authored-by: Kattni <[email protected]>
@ncoghlan
Copy link
Contributor

This is close enough to the bug fix/enhancement boundary that I've asked for RM confirmation before merging it.

@ncoghlan ncoghlan self-assigned this Jun 22, 2025
@hugovk
Copy link
Member

hugovk commented Jun 23, 2025

This is okay for 3.14, thanks!

@hugovk hugovk merged commit a843fec into python:3.14 Jun 23, 2025
49 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip issue skip news type-bug An unexpected behavior, bug, or error

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants