Standardise usage requirements and assessment#7764
Merged
Conversation
Alhadis
requested changes
Jan 14, 2026
Co-authored-by: John Gardner <gardnerjohng@gmail.com>
Alhadis
previously approved these changes
Jan 14, 2026
Co-authored-by: John Gardner <gardnerjohng@gmail.com>
lildude
commented
Jan 14, 2026
Alhadis
approved these changes
Jan 14, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
We've been using the "temporary" usage requirements and assessment approach detailed in #5756 since GitHub changed its Search.
Nothing better has come about since then so I think it's time we solidify these in the CONTRIBUTING.md file and make them easily referencable.
I've also taken the opportunity to use GitHub markdown alerts to bring attention to some of our important points.
Closes #5756