v0.0.0.1 feat: add duplicate upload rejection reason - #332
Merged
Conversation
Member
Author
|
STAFF ENGINEER REVIEW: APPROVED — Upload duplicate rejection reason is clean. Checked the upload-review callback path, duplicate rejection mapping, localization, payout side effects, sensitive upload/moderation surface, and public-repo secret guard. The new Verification: GitHub |
Member
Author
|
✅ Approved + merged. |
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
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.
Summary
🔁 Баянrejection button to the existing upload-review reason row.reject_duplicatethrough the normal rejection path and storeMemeStatus.REJECTED.Test coverage
Coverage: 6/6 changed behavior paths tested (100%); no untested gaps identified.
Verification
pytest tests/tgbot/test_upload_moderation.py -q— 8 passed.ruff check src/ tests/— passed.ruff format --check src/ tests/— passed.git diff --check— passed.Pre-landing review
Scope and documentation
Test plan
The release test plan is recorded in the local gstack project artifacts. The user-visible path is covered at callback level because this workflow runs inside the private Telegram moderation chat rather than a browser UI.
Generated with Codex