Clarify ban evasion policy #137298
Merged
Clarify ban evasion policy #137298
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
kbeyls
requested review from
AaronBallman,
JDevlieghere,
cyndyishida,
dwblaikie,
sstamenova and
tlattner
sstamenova
approved these changes
Apr 25, 2025
JDevlieghere
approved these changes
Apr 25, 2025
cyndyishida
approved these changes
Apr 28, 2025
GeorgeARM
pushed a commit
to GeorgeARM/llvm-project
that referenced
this pull request
May 7, 2025
This documents what the Code of Conduct committee has decided to do when an attempt to evade a ban is detected.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
This documents what the Code of Conduct committee has decided to do when an attempt to evade a ban is detected.