Skip to content

Update to Requesting Review rules #317

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.

Sign up for GitHub

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

Merged
wescopeland merged 1 commit into from
Feb 5, 2026
Merged

Update to Requesting Review rules #317

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/developer-docs/am-i-ready-for-review.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,10 @@ Tips for testing:
# Requesting a Review

Before you request a review on your set, it must be clear of bad practices. In particular, you must use [AutoCR](https://authorblues.github.io/retroachievements/AutoCR/) and go through every issue it flags. As with any automatic feedback tool, it is not perfect, and flags can sometimes be ignored. It is still invaluable to identify issues with your set, especially while you are still learning. In your Ready for Review post on #jr-devs-request, you must:
- Have had the claim for at least 7 days
- Have an approved Set Plan for at least 7 days
- Explain your testing process
- Link to the Unpublished achievement page for your game
- Include a link to Set Plan Review thread
- Link to the AutoCR page for the set (using the Load by Game ID feature)
- Explain why any issue flagged by AutoCR has been ignored

Expand Down