Find an Issue
The right first issue is small and boring. That's a feature, not a problem.
What you'll learn
A good first issue is small, clearly described, and doesn't require understanding the whole codebase. Avoid issues that are vague, already claimed by someone else, or that touch code you don't yet understand. There'll be time for those later. A fix-a-bug or fix-a-typo issue can only be done once, so if you're not the first person here, it may already be closed. That's normal, not a dead end: "Add yourself to CONTRIBUTORS.md" is designed to never run out, since everyone's addition is its own line and nobody's work conflicts with anyone else's.
Do this
- Filter the practice repository's issues by the "pull-practice-issue" label.
- Read the full issue, including comments. Someone may already be working on it.
- Check that it has clear acceptance criteria before you commit to it.
- Nothing open and unclaimed? Look for "Add yourself to CONTRIBUTORS.md". It's always available, and it's a completely valid first pull request.
Try it
Pick one open, unclaimed issue and leave a comment saying you're working on it.
Check your work
You've picked one issue, and you could explain to someone else exactly what "done" looks like for it.