Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[3.14] patchcheck: use URL paths to identify upstream remote (GH-135806) #135808

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: 3.14
Choose a base branch
from

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting review 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.

3 participants