This guide is for listed approvers and repository administrators reviewing game and app preset issues.
- Open the oldest validated request in the game queue or app queue. Check the latest validation comment after the last issue edit.
- For games, check the IGDB URL and resolved GameDB record. For apps, inspect the official URL and optional image URL. App requests always need a separate review, including when a trusted contributor submits them.
- Check the selected host OS for Native, GOG, or app requests. For Steam, Epic Games, and Microsoft Store, check the launch ID, generated commands, and which platforms the game actually supports. For Emulator, confirm the manual command and placeholders are portable. Review setup notes against the preset guidelines and Sunshine examples. Automated validation checks syntax and never runs commands. ProtonDB reports inform Linux compatibility for Steam but are not an approval gate.
- Search the published record for the same method, host OS when present, and emulator variant. A replacement must identify an existing preset issue and explain the change.
- Comment
@LizardByte-bot approveto enter the approval queue. The bot addsapprove-queueand startsapprove-presetwhen the active slot is free. It revalidates against IGDB and GameDB before writing to thedatabasebranch.
The approval workflow comments its result. A successful approval closes the issue and requests a Pages rebuild. On failure, it removes the issue from the queue so the next request can proceed; fix the issue and queue it again. The approve-preset label remains on successfully closed issues for the approved count badge.
The trusted user list lives in auto_approved_users.json. Add or remove an approver by changing that file in a reviewed pull request. A listed game submitter is queued automatically after successful validation. Repository administrators can also approve by comment.