starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Please help with pull request reviews! #4380

New issue

Open

opened 2026-02-28 04:00:24 -05:00 by deekerman · 13 comments

deekerman commented

2026-02-28 04:00:24 -05:00

Owner

Originally created by @CommanderStorm on GitHub (Oct 25, 2025).

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.

Originally created by @CommanderStorm on GitHub (Oct 25, 2025). 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](https://github.com/louislam/uptime-kuma/blob/master/.github/REVIEW_GUIDELINES.md) 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.

deekerman added the

discussion

help wanted

labels

2026-02-28 04:00:24 -05:00

deekerman commented

2026-02-28 04:00:34 -05:00

Author

Owner

@lupaulus commented on GitHub (Oct 26, 2025):

Asking if AI Reviews or add CI Linter/Rules can help to reduce the workload ?

I find personally they reduce, some pure 'developers' mistakes or bugs,
that a new features or fix can introduce to the code.

I try to help the best I can do

I can ask my university students, if they are someone interested to help, that can enhanced their Curriculum Vitae.

Best Regards

@lupaulus commented on GitHub (Oct 26, 2025): Asking if AI Reviews or add CI Linter/Rules can help to reduce the workload ? I find personally they reduce, some pure 'developers' mistakes or bugs, that a new features or fix can introduce to the code. I try to help the best I can do I can ask my university students, if they are someone interested to help, that can enhanced their Curriculum Vitae. Best Regards

deekerman commented

2026-02-28 04:00:36 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Oct 27, 2025):

Asking if AI Reviews or add CI Linter/Rules can help to reduce the workload ?

Maybe?
Most review issues aren’t recurring enough to justify rules, and the AI review tools I tried (like Coderabbit) tend to produce a lot of noise. Maybe that can be tuned, or they have improved.
You likely have more experience in this than I have, are there tools you can recomend?

What would be nice to enable is Copilot reviews. It is fairly helpful for catching typos.
@louislam could you enable this in the settings?

I can ask my university students, if they are someone interested to help, that can enhanced their Curriculum Vitae.

Reading “weird code” (all code written by others is weird) is actually a great way to develop better taste.
Not sure if it improves a CV directly, but being a better Software engineer does.

If I could give one piece of advice to your students, it would rather be:

"Do quality work."

Why?
Because dumping untested, vibe-coded contributions doesn’t make you more employable - but doing something well absolutely does.

@CommanderStorm commented on GitHub (Oct 27, 2025): > Asking if AI Reviews or add CI Linter/Rules can help to reduce the workload ? Maybe? Most review issues aren’t recurring enough to justify rules, and the AI review tools I tried (like Coderabbit) tend to produce a lot of noise. Maybe that can be tuned, or they have improved. You likely have more experience in this than I have, are there tools you can recomend? What would be nice to enable is Copilot reviews. It is fairly helpful for catching typos. @louislam could you enable this in the settings? > I can ask my university students, if they are someone interested to help, that can enhanced their Curriculum Vitae. Reading “weird code” (all code written by others is weird) is actually a great way to develop better taste. Not sure if it improves a CV directly, but being a better Software engineer does. If I could give one piece of advice to your students, it would rather be: "Do quality work." Why? Because dumping untested, vibe-coded contributions doesn’t make you more employable - but doing something well absolutely does.

deekerman commented

2026-02-28 04:00:36 -05:00

Author

Owner

@louislam commented on GitHub (Oct 27, 2025):

Just enabled in the ruleset, not sure if it is enough though.

@louislam commented on GitHub (Oct 27, 2025): Just enabled in the ruleset, not sure if it is enough though. <img width="300" height="373" alt="Image" src="https://github.com/user-attachments/assets/be68ea93-992a-4be7-849a-a772195c2f81" />

deekerman commented

2026-02-28 04:00:36 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Nov 9, 2025):

@louislam could you turn off Review new pushes branch protections?
One intial review is likely best for spam avoidance.

@CommanderStorm commented on GitHub (Nov 9, 2025): @louislam could you turn off `Review new pushes` branch protections? One intial review is likely best for spam avoidance.

deekerman commented

2026-02-28 04:00:36 -05:00

Author

Owner

@louislam commented on GitHub (Nov 9, 2025):

Just unchecked.

@louislam commented on GitHub (Nov 9, 2025): Just unchecked.

deekerman commented

2026-02-28 04:00:36 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Nov 9, 2025):

Thanks ❤️

@CommanderStorm commented on GitHub (Nov 9, 2025): Thanks ❤️

deekerman commented

2026-02-28 04:00:36 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 24, 2025):

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!

50 down, 45 to go

@CommanderStorm commented on GitHub (Dec 24, 2025): > 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! 50 down, 45 to go

deekerman commented

2026-02-28 04:00:36 -05:00

Author

Owner

@louislam commented on GitHub (Jan 25, 2026):

After reading: https://www.reddit.com/r/programming/comments/1ql0w5p/overrun_with_ai_slop_curl_scraps_bug_bounties_to/

I’ve also decided to disallow similar pull requests.
People are just rushing us to earn bug bounty money.

Any pull requests listed on Gittensor will be closed.
https://gittensor.io/miners/repository?name=louislam%2Fuptime-kuma

Not sure about other platforms. Let me know if you know any.

For pure AI usage (not bug-bounty driven), it’s acceptable when used to:

fix small issues
correct grammar
help understand the codebase
act as auto-complete

But if someone just feeds the issue to a code agent, generates code + LLM description, then pings for review without checking anything

Depending on my mood, you might get banned immediately.

Wall of Shame (started january 2026)

@louislam commented on GitHub (Jan 25, 2026): After reading: https://www.reddit.com/r/programming/comments/1ql0w5p/overrun_with_ai_slop_curl_scraps_bug_bounties_to/ I’ve also decided to disallow similar pull requests. People are just rushing us to earn bug bounty money. Any pull requests listed on Gittensor will be closed. https://gittensor.io/miners/repository?name=louislam%2Fuptime-kuma Not sure about other platforms. Let me know if you know any. For pure AI usage (not bug-bounty driven), it’s acceptable when used to: - fix small issues - correct grammar - help understand the codebase - act as auto-complete But if someone just feeds the issue to a code agent, generates code + LLM description, then pings for review without checking anything Depending on my mood, you might get **banned** immediately. ### Wall of Shame (started january 2026) - https://github.com/louislam/uptime-kuma/issues/6260#issuecomment-3897470982 - https://github.com/louislam/uptime-kuma/pull/6950 - https://github.com/louislam/uptime-kuma/issues/6924 - https://github.com/louislam/uptime-kuma/pull/6942 - https://github.com/louislam/uptime-kuma/pull/6828 - https://github.com/louislam/uptime-kuma/pull/6910 - https://github.com/louislam/uptime-kuma/pull/6901 - https://github.com/louislam/uptime-kuma/pull/6667 - https://github.com/louislam/uptime-kuma/pull/6550 - https://github.com/louislam/uptime-kuma/pull/6416 - https://github.com/louislam/uptime-kuma/pull/6235 - https://github.com/louislam/uptime-kuma/pull/6155 - https://github.com/louislam/uptime-kuma/pull/6137 - https://github.com/louislam/uptime-kuma/pull/6959 - https://github.com/louislam/uptime-kuma/pull/6961 - https://github.com/louislam/uptime-kuma/pull/6926 - https://github.com/louislam/uptime-kuma/pull/7001 - https://github.com/louislam/uptime-kuma/pull/7012 - https://github.com/louislam/uptime-kuma/pull/7018 - https://github.com/louislam/uptime-kuma/pull/7049 - @Badrangui1 AI slop security report

deekerman commented

2026-02-28 04:00:36 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jan 25, 2026):

Thanks, I think this is a good call, unless someone wants to contribute in the reviews.
Currently this was not sustainable.

@CommanderStorm commented on GitHub (Jan 25, 2026): Thanks, I think this is a good call, unless someone wants to contribute in the reviews. Currently this was not sustainable.

deekerman commented

2026-02-28 04:00:36 -05:00

Author

Owner

@ryangurn commented on GitHub (Feb 3, 2026):

@CommanderStorm and/or @louislam how can I help with review. I love uptime kuma and would be more than willing to assist with PR review.

I do not have the deepest understanding of the codebase so I might review along side y'all before I start reviewing completely on my own, but I am more than willing to help! Let me know how I can be most useful to this process!

@ryangurn commented on GitHub (Feb 3, 2026): @CommanderStorm and/or @louislam how can I help with review. I love uptime kuma and would be more than willing to assist with PR review. I do not have the deepest understanding of the codebase so I might review along side y'all before I start reviewing completely on my own, but I am more than willing to help! Let me know how I can be most useful to this process!

deekerman commented

2026-02-28 04:00:36 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Feb 3, 2026):

Any help is appreciated

@CommanderStorm commented on GitHub (Feb 3, 2026): Any help is appreciated

deekerman commented

2026-02-28 04:00:36 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Feb 13, 2026):