Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Force github workflow catch PyTorch commit from release/2.5 branch for PyTorch/XLA r2.5 branch #8078

Merged
merged 2 commits into from
Sep 27, 2024
Merged

Force github workflow catch PyTorch commit from release/2.5 branch for PyTorch/XLA r2.5 branch #8078

merged 2 commits into from
Sep 27, 2024

Conversation

ManfeiBai
Copy link
Collaborator

@ManfeiBai ManfeiBai commented Sep 26, 2024 •
edited
Loading

Force github workflow catch PyTorch commit from release/2.5 branch for PyTorch/XLA r2.5 branch

@ManfeiBai ManfeiBai marked this pull request as ready for review September 26, 2024 22:21
@JackCaoG
Copy link
Collaborator

not sure why linter is failing

@ManfeiBai
Copy link
Collaborator Author

Details

linter failed due to formal cherry-pick PR: #8008 was supposed to be merged with #8052 together, and #8052 fixed the linter failure;

since #8077 also fixed the linter failure, rebase will fix this linter failure

@ManfeiBai ManfeiBai merged commit 5cc01cf into r2.5 Sep 27, 2024
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@JackCaoG JackCaoG JackCaoG approved these changes

@will-cromar will-cromar Awaiting requested review from will-cromar

@miladm miladm Awaiting requested review from miladm

@lsy323 lsy323 Awaiting requested review from lsy323

Assignees
No one assigned
Labels
2.5 release
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ManfeiBai @JackCaoG