{44} Good First Bugs (105 matches)

These tickets have been marked as being a "good first bug" for new contributors.

First bugs aren't necessarily "easy," though some are. These bugs are meant to be well-contained. They are designed to help get you familiar with WordPress core code, processes, and contributing, not send you down a rabbit hole for days on end. Whoever marked the ticket likely explained in the ticket why they did so, giving you a good starting point from which to work.

The person who marked the ticket as a "good first bug" — as well as other members of the community — will help you through this ticket by providing feedback along the way. Start by getting a handle on the problem, verifying that you can reproduce it, drawing up a plan of attack, and then creating a patch.

The ​Core Contributor Handbook should have some good reference materials for you, including ​an overview of the codebase, ​coding standards, ​how we use our bug tracker, and various tutorials and guides like setting up a development environment and creating patches.

If you're not a contributor who is just starting out, please find one of the hundreds of other bugs to patch!

If this report is running low or nothing catches your eye, try this report of tickets that need a patch. If you like unit tests, you can check out how automated testing is set up ​in the handbook, then browse the tickets that need unit tests. Or, if you want to contribute by testing patches, here are some patches that have been marked as specifically needing testing.