Create profanity filter workflow and accompanying label #883
Conversation
This file contains 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
beeankha
added
the
type::task
conda-bot
added
the
cla-signed
beeankha
commented
Feb 29, 2024
.github/global.yml
Outdated
| @@ -41,6 +41,9 @@ | |||
| - name: dependencies | |||
| description: '[bot] PRs that update a dependency file' | |||
| color: '#0366d6' | |||
| - name: profane content 🤬 | |||
| description: 'Either the title or body text contains profanity' | |||
| color: 'FBCA04' | |||
There was a problem hiding this comment.
This label is required (if not previously implemented a new one gets created), please see Label requirements section of the profanity filter's README
beeankha
added
the
pending::discussion
|
@beeankha Following the discussion in March about this, could you provide an update on this please? |
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.
Description
Due to a recent incident involving a community member posting a conda issue that included profanity (in violation of CoC guidelines), it appears that there might be some good use for including a profanity filter across the conda GH org.