Add benchmarking provision #648
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
anti-anti-benchmarking |
1 similar comment
|
anti-anti-benchmarking |
ghost
approved these changes
Oct 3, 2022
|
Good |
|
Okay |
khxu
approved these changes
Feb 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GitHub is adding an anti-anti-benchmarking provision to our Additional Product Terms.
This change is intended to impact only those who:
If you meet the above criteria and benchmark against a GitHub product or service, this addition makes clear that you waive your anti-benchmarking provision as it pertains to GitHub. This allows GitHub to benchmark against your product or service.
It is important to note that GitHub currently allows benchmarking of its products and services. This proposal does nothing to alter that except in the event that you do not wish to waive your anti-benchmarking provision.
This update will go into effect after the 30-day notice and comment period on October 31, 2022.