Skip to content

[3.7] bpo-40548: Fix "Check for source changes (pull_request)" GH Action job (GH-21806) #92342

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

Merged
merged 4 commits into from
Sep 2, 2022

Conversation

miss-islington
Copy link
Contributor

On Git 2.28, "git diff master..." (3 dots) no longer works when
"fetch --depth=1" is used, whereas it works on Git 2.26.

Replace "..." (3 dots) with ".." (2 dots) in the "git diff" command
computing the list of modified files between the base branch and the
PR branch.
(cherry picked from commit eaa5517)

Co-authored-by: Victor Stinner [email protected]

pythonGH-21806)

On Git 2.28, "git diff master..." (3 dots) no longer works when
"fetch --depth=1" is used, whereas it works on Git 2.26.

Replace "..." (3 dots) with ".." (2 dots) in the "git diff" command
computing the list of modified files between the base branch and the
PR branch.
(cherry picked from commit eaa5517)

Co-authored-by: Victor Stinner <[email protected]>
@miss-islington
Copy link
Contributor Author

@vstinner: Status check is done, and it's a success ✅ .

@vstinner
Copy link
Member

vstinner commented May 5, 2022

Why do you need this backport today?

@JelleZijlstra
Copy link
Member

See #92334

@miss-islington
Copy link
Contributor Author

@vstinner: Status check is done, and it's a failure ❌ .

1 similar comment
@miss-islington
Copy link
Contributor Author

@vstinner: Status check is done, and it's a failure ❌ .

@erlend-aasland
Copy link
Contributor

Do we still want to pursue this in the 3.7 branch?

@ned-deily ned-deily merged commit 9d58933 into python:3.7 Sep 2, 2022
@miss-islington miss-islington deleted the backport-eaa5517-3.7 branch September 2, 2022 03:28
@ned-deily
Copy link
Member

Do we still want to pursue this in the 3.7 branch?

Sorry, this should have been merged earlier; it slipped off my radar. Thanks for the backport!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants