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.

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

Explictly use Py310 in github workflows #820

Merged
merged 1 commit into from
Jan 16, 2025

Conversation

sampathweb
Copy link
Collaborator

I accidentaly merged the PR. I should just mark it as "Ready for Pull".

Copy link
Contributor

@hertschuh hertschuh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks!

@sampathweb sampathweb added the ready to pull Ready to be merged into the codebase label Jan 15, 2025
copybara-service bot pushed a commit that referenced this pull request Jan 16, 2025
Imported from GitHub PR #820

I accidentaly merged the PR. I should just mark it as "Ready for Pull".
Copybara import of the project:

--
6736320 by Ramesh <[email protected]>:

Explictly use Py310 in github workflows

Merging this change closes #820

FUTURE_COPYBARA_INTEGRATE_REVIEW=#820 from sampathweb:fix-code-linter 6736320
PiperOrigin-RevId: 715982921
@copybara-service copybara-service bot merged commit 384111f into keras-team:master Jan 16, 2025
10 checks passed
@github-actions github-actions bot removed the ready to pull Ready to be merged into the codebase label Jan 16, 2025
@sampathweb sampathweb deleted the fix-code-linter branch January 16, 2025 01:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants