-
Notifications
You must be signed in to change notification settings - Fork 438
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
🌱 docs(footer): Add trademark disclaimer #3132
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mariasalcedo The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Welcome @mariasalcedo! |
Hi @mariasalcedo. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Looks reasonable to me, thanks for taking care of this @mariasalcedo! /ok-to-test |
@mikemorris Thanks! Please add the |
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.
Thanks @mariasalcedo! Unfortunately we're going to need to hold off on merging this until cncf/foundation#809 is resolved.
/hold
Co-authored-by: Rob Scott <[email protected]>
New changes are detected. LGTM label has been removed. |
LGTM pending resolution of the license question. |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Adds correct trademark disclaimer, as part of our ongoing effort to cncf/techdocs#198
Which issue(s) this PR fixes:
Fixes #2735
Does this PR introduce a user-facing change?: