Help us merge the PRs you like by, in order of difficulty:
- Showing your approval using reactions on the first post of the Github issue
- Post constructive comments and try to convince other people of its usefulness if needed.
Don't just do "+1" or "looks good!" as that's annoying and not constructive.
- Bumping PRs in the #minetest-dev IRC channel to ask devs to review them (don't ping anyone though as that's rude!)
- Test to find bugs. Do it with a high attention of detail, and say how you tested it.
We'll trust your testing more if you say what you've done and if you consistently find issues in things you test
Also, look out for this label:
- Review the PR to find issues. Anyone can use the review feature to point out issues they find.
Pointing out issues before a dev has to means we can use our reviewing time more productively.
Don't just approve a PR as we'll just assume you're doing it because you like the concept.
Use the emoji reactions to show your approval. Only use the review feature if you've checked the code.
Make sure to say whether you've tested it (and how) and also how detailed your code review was.
- Kidnap a dev (note: may be illegal).
Before I was a developer, I reviewed PRs for easily two years.
In the mean time, we've already made some progress with Lua Unit Tests and code clean ups which should help with reviewing PRs and avoiding regressions. Hopefully we'll eventually get to a state where a large number of important issues are caught by testing, although this will be difficult
Interested in how Minetest is developed? Have a look at the Developer Road Maps and Worklists, the To do list on the dev wiki, and consider watching the engine repository.