Skip to content

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

Merged
hugovk merged 1 commit intopython:3.13from
miss-islington:backport-ac9d37c-3.13
Jun 23, 2025
Merged

[3.13] patchcheck: use URL paths to identify upstream remote (GH-135806)#135809
hugovk merged 1 commit intopython:3.13from
miss-islington:backport-ac9d37c-3.13

Conversation

@miss-islington
Copy link
Copy Markdown
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 kattni@kattni.com

* 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 <kattni@kattni.com>
@ncoghlan
Copy link
Copy Markdown
Contributor

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

@hugovk
Copy link
Copy Markdown
Member

hugovk commented Jun 23, 2025

Thomas has confirmed this is okay for 3.13 (as long as it goes into 3.14 as well, which it has).

Thanks!

@hugovk hugovk merged commit b79e64b into python:3.13 Jun 23, 2025
41 checks passed
@miss-islington miss-islington deleted the backport-ac9d37c-3.13 branch January 2, 2026 18:06
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