-
Notifications
You must be signed in to change notification settings - Fork 155
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
fix: changeover unspecified to inherited #603
Conversation
Co-authored-by: Tres Seaver <tseaver@palladion.com>
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
1 similar comment
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
Co-authored-by: Tres Seaver <tseaver@palladion.com>
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
1 similar comment
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
@tseaver should I go back and change the commits so I write them rather than just including your suggestions? Or are you able to get the Google/Github CLA thing taken care of from your end? |
@googlebot I consent. |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
@Breathtender As a Googler, you should be able to manually flip the label from |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
All changes resolved, and approval was given.
Ah, seems we still need a review, after navigating some strange lint issues. |
google/cloud/storage/bucket.py
Outdated
"""Setting for public access prevention policy. Options are 'inherited' (default) or 'enforced'. | ||
See: https://cloud.google.com/storage/docs/public-access-prevention |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still needs the blank line to separate summary from body.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah strange, I think the blank line caught the linter, which is why I changed it back. But perhaps I had just left white space in the line which was the issue.
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
@Breathtender One more manual flip of the CLA flag, and you should be good to go. |
* fix: changeover unspecified to inherited * Update google/cloud/storage/bucket.py Co-authored-by: Tres Seaver <tseaver@palladion.com> * Apply suggestions from code review Co-authored-by: Tres Seaver <tseaver@palladion.com> * remove dup line * Apply suggestions from code review Co-authored-by: Tres Seaver <tseaver@palladion.com> * Update tests/unit/test_bucket.py Co-authored-by: cojenco <cathyo@google.com> * lint fix * one more lint fix * line Co-authored-by: Tres Seaver <tseaver@palladion.com> Co-authored-by: cojenco <cathyo@google.com>
* fix: changeover unspecified to inherited * Update google/cloud/storage/bucket.py Co-authored-by: Tres Seaver <tseaver@palladion.com> * Apply suggestions from code review Co-authored-by: Tres Seaver <tseaver@palladion.com> * remove dup line * Apply suggestions from code review Co-authored-by: Tres Seaver <tseaver@palladion.com> * Update tests/unit/test_bucket.py Co-authored-by: cojenco <cathyo@google.com> * lint fix * one more lint fix * line Co-authored-by: Tres Seaver <tseaver@palladion.com> Co-authored-by: cojenco <cathyo@google.com>
Fixes #597 🦕