-
Notifications
You must be signed in to change notification settings - Fork 738
Added NSFW Content Detection #108
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
Open
harlanenciso112
wants to merge
20
commits into
Roshanjossey:main
Choose a base branch
from
harlanenciso112:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
test5 name in file
Add controls for offensive or NSFW content
xarical
added a commit
to xarical/code-contributions
that referenced
this pull request
Jun 21, 2025
- Add toxicity-check.yml workflow with check_toxicity.py script for automatic content moderation from Roshanjossey#108 (resolves Roshanjossey#27) - Refactor toxicity-check.yml and check_toxicity.py to use the GitHub CLI and use gemma-9b-it served by Groq (per Roshanjossey#27 (comment)) respectively - Rename toxicity-check.yml and check_toxicity.py to auto-pr-merge.yml and check_pr.py respectively Co-authored-by: harlanenciso112 <harsanenciso@gmail.com>
xarical
added a commit
to xarical/code-contributions
that referenced
this pull request
Jun 21, 2025
- Add toxicity-check.yml workflow with check_toxicity.py script for automatic content moderation from Roshanjossey#108 (resolves Roshanjossey#27) - Refactor toxicity-check.yml and check_toxicity.py to use the GitHub CLI and use gemma-9b-it served by Groq (per Roshanjossey#27 (comment)) respectively - Rename toxicity-check.yml and check_toxicity.py to auto-pr-merge.yml and check_pr.py respectively Co-authored-by: harlanenciso112 <harsanenciso@gmail.com>
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.
Hi @Roshanjossey,
I read the issue where you mentioned your interest in adding a restriction to control offensive or NSFW content, so I decided to help with that.
How I implemented it:
I used a pre-trained model from Hugging Face specialized in detecting offensive language.
Implemented a function that analyzes the input content and assigns a probability score to potentially inappropriate messages.
Fixez #27 "One additional constrain I'd like for this is to have checks for offensive or NSFW content."