Open challenge reports to readers, and spare reported challenges from auto-archiving - #1281
Merged
Merged
Conversation
… auto-archiving Filing a report already posts a public challenge comment naming the reporter and quoting what they wrote, so what a report says is public either way. Add GET /challenge/:challengeId/reports, which returns every report on a challenge to anyone, signed in or not, with the parts that are not public stripped: the email a reporter volunteered for follow-up, and the admin side of the triage record. Status and reviewedAt survive, so a reader can see a report was dealt with. The triage queue itself is unchanged and still superusers only. The nightly stale-challenge archiver now skips challenges carrying an open report. Archiving one dropped it out of the admin triage queue, which defaults to challenges that are still active, before anyone had ruled on it. Manual archiving is untouched -- that is the remedy an admin reaches for when actioning a report.
|
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.
Filing a report already posts a public challenge comment naming the reporter and quoting what they wrote, so what a report says is public either way. Add GET /challenge/:challengeId/reports, which returns every report on a challenge to anyone, signed in or not, with the parts that are not public stripped: the email a reporter volunteered for follow-up, and the admin side of the triage record. Status and reviewedAt survive, so a reader can see a report was dealt with. The triage queue itself is unchanged and still superusers only.
The nightly stale-challenge archiver now skips challenges carrying an open report. Archiving one dropped it out of the admin triage queue, which defaults to challenges that are still active, before anyone had ruled on it. Manual archiving is untouched -- that is the remedy an admin reaches for when actioning a report.