louislam/uptime-kuma

Please help with pull request reviews!

Open

#6260 opened on Oct 26, 2025

View on GitHub
 (21 comments) (18 reactions) (0 assignees)JavaScript (86,760 stars) (7,844 forks)batch import
discussionhelp wanted

Description

We have a huge number of open pull requests, and it's unfortunate that so many of them stay open for so long before being reviewed or merged. I'd like to change this situation.

[!IMPORTANT] Obviously, there are more than pull requests. Contributing to features, bugs, docs or by helping people are great ways to empower others (and thus you!).

The main bottleneck that we have currently is more pull requests being created than the maintainers can review each week. Reviewing PRs is often time consuming, and with the best will in the world there's only so many that I can manage each week. It's also often a bit emotionally draining for me, since I don't enjoy saying no to PRs, or asking other volunteers to do even more work (e.g. making more changes to their PR). But rather than having fewer PRs opened each week (which would be a bad situation), I would like to get more reviews completed each week instead.

The best thing that you can do to help is to review someone else's PR. Don't worry, there's over 95 open today, I'm sure you can find one of interest to you! Please take a look at it, read through it, have a think about the problem and the proposed solution and see what comes to mind. Maybe you'll spot that there's actually an underlying problem that should be solved instead (https://github.com/louislam/uptime-kuma/issues/6200 is a great example of this), or you would have a different approach if you did it yourself, or you apply some of our "internal" pr reiew guidelines and can help other contributors shape up their PR. That way the PR will become easier for the maintainers to review and merge when they get to it.

All of this helps share the workload for the maintainers. And it's the main path to becoming a maintainer yourself! I would also love to see a few more maintainers in the team.

I'm happy to help anyone who is helping out with the work of reviewing PRs, since I think it's the main thing that is limiting our progress right now.

Contributor guide