Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Numbering system for variants?

Open
#5 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Domain
content

Research direction

No files, tests, or entry points are named. Review the repository's existing sprite and variant data conventions, then use the discussion to determine whether a numbering approach is wanted and what the accepted handling of alternate forms would be; done means an agreed project direction rather than an implementation defined by this issue.

Written by the indexing model from the issue text.

Description

question

I'm using these sprites in a personal project and supplementing them with artwork from Sun & Moon. I'd like to contribute back to the PokeAPI project by submitting a pull request with this content, along with whatever data I contribute to the core. However, there are many variants (Alola forms & identical Pokemon species with different appearances and typings), and I'm curious how the project tackles these.

Dominant language
Python
Stars
1.7k
Forks
378
Avg merge
22h 18m
Merged PRs (30d)
25

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PokeAPI/sprites

All issues in PokeAPI/sprites

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.