How the SM'S DEX roster works
Visitors submit a character through the site's form. A GitHub issue starts validation, then a pull request gives Shivam a review step before publication.
From form to issue
The Add Pokémon form collects a GitHub username, species, types, status, and short dex entry. Submitting opens a prefilled issue in the site's GitHub repository. The issue is the public record of what a visitor entered.
Validation and review
A GitHub Actions workflow runs when a qualifying issue opens, changes, or receives a label. It parses the issue, runs the submission validator, writes a roster entry, and opens or updates a pull request. Validation errors are posted back to the issue. Shivam reviews the generated JSON before merging the pull request.
Why use a pull request
A public form should not publish arbitrary text instantly. Review keeps the roster intentional while leaving a visible path from submission to entry. The roster data lives in the repository, so the site can build from a checked-in copy.
Try the form on the homepage, or read the broader project overview.