-
Notifications
You must be signed in to change notification settings - Fork 286
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
Add a way to track organizer issues #939
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #939 +/- ##
==========================================
+ Coverage 81.01% 81.24% +0.23%
==========================================
Files 95 98 +3
Lines 2860 2938 +78
Branches 269 271 +2
==========================================
+ Hits 2317 2387 +70
- Misses 492 499 +7
- Partials 51 52 +1
... and 4 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Co-authored-by: Mark Walker <theshow@gmail.com>
Co-authored-by: Mark Walker <theshow@gmail.com>
Co-authored-by: Mark Walker <theshow@gmail.com>
Co-authored-by: Mark Walker <theshow@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think this looks good with those improvements in 👍
Every now and then community members report issues to do with Django Girls workshop organizers through email. However, since email is separate from the CMS, these issues fall through the cracks and are only uncovered when the same organizer has another issue reported against them.
This pull request introduces:
OrganizerIssue
model to track issues to do with organizers.is_blacklisted
to the user model.[TO DO]
.