feat: Slash after N consecutive epochs of inactivity#16700
Merged
spalladino merged 1 commit intonextfrom Sep 3, 2025
Merged
Conversation
spalladino
force-pushed
the
palla/slash-consecutive-epochs-inactive
branch
from
358bae7 to
30a0126
Compare
Instead of slashing on inactivity immediately, the sentinel now waits until the last N epochs for which it has data for the offender also match the inactivity threshold. Defaults to 1, so the behaviour is the same as the current one.
spalladino
force-pushed
the
palla/slash-consecutive-epochs-inactive
branch
from
30a0126 to
8ee262b
Compare
just-mitch
approved these changes
Sep 3, 2025
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
ludamad
pushed a commit
that referenced
this pull request
Dec 16, 2025
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
2 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.
Instead of slashing on inactivity immediately, the sentinel now waits until the last N epochs for which it has data for the offender also match the inactivity threshold.
Defaults to 1, so the behaviour is the same as the current one.