Skip to content

Conversation

@SaulRojas1505
Copy link

@SaulRojas1505 SaulRojas1505 commented Dec 20, 2024

Description of the change

Motivation

Type of change

Choose one: (Bug fix | Feature request | Documentation | Other)

Checklist

  • I have performed a self-review of my code.
  • I have added detailed comments to my code where applicable.
  • I have verified that my change does not break existing code.
  • My PR is based on the latest changes of the main branch (if unsure, please run git pull --rebase upstream main).
  • I am familiar with the Google Style Guide for the language I have coded in.
  • I have read through the Contributing Guide and signed the Contributor License Agreement.

@google-cla
Copy link

google-cla bot commented Dec 20, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@SaulRojas1505 SaulRojas1505 marked this pull request as ready for review December 21, 2024 15:06
@SaulRojas1505 SaulRojas1505 requested a review from a team as a code owner December 21, 2024 15:06
@github-actions github-actions bot added status:awaiting review PR awaiting review from a maintainer component:documentation Update docs labels Dec 21, 2024
@joefernandez
Copy link
Contributor

This change is a significant change and yet not explained at all. Closing.

@github-actions github-actions bot removed the status:awaiting review PR awaiting review from a maintainer label May 5, 2025
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.

2 participants