Merged
Conversation
Posts a public summary of a user's moderation history so the whole mod team has context when responding to incidents. Includes report count, anonymous report count, message/channel spread, date range, peak daily count, and a link to the user's log thread. Co-Authored-By: Claude Opus 4.6 <[email protected]>
The alreadyReported check matched any existing report for a message regardless of reason, preventing different report types (e.g., Track after an anonymous report) from creating separate DB records. Now matches on both message ID and reason so each report type is tracked independently. Co-Authored-By: Claude Opus 4.6 <[email protected]>
Kysely migrations used c.defaultTo("CURRENT_TIMESTAMP") which stores
the quoted string as the default instead of the SQL expression. This
caused all created_at values to be the string "CURRENT_TIMESTAMP",
breaking date parsing in /modreport.
Fix inserts to explicitly set created_at and add a migration to
backfill existing rows with datetime('now').
Co-Authored-By: Claude Opus 4.6 <[email protected]>
Add richer context to the modreport embed: reason breakdown, report recency/velocity, per-channel breakdown, reporter diversity, sparkline histogram, and a chronological mod action timeline. Restructure the embed to use fields for logical grouping. Also introduces the mod_actions table and records kick/ban/timeout events from the existing mod action log flow. Co-Authored-By: Claude Opus 4.6 <[email protected]>
vcarl
force-pushed
the
mod-bot_user-reports
branch
from
6eb348c to
29cb355
Compare
Member
Author
|
Smoke Test Results
Tested commit: |
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
1 participant
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.
Introduce a
/modreportslash command to summarize how many times a user has been reported, including when their first report happened and when the most recent report happened. Revises database behavior to record more reports than previously.