Skip to content

gitea: add reminder bot for ObsStaging failures and pending reviews#3288

Open
Volcano28 wants to merge 2 commits intoopenSUSE:masterfrom
Volcano28:reminder-bot
Open

gitea: add reminder bot for ObsStaging failures and pending reviews#3288
Volcano28 wants to merge 2 commits intoopenSUSE:masterfrom
Volcano28:reminder-bot

Conversation

@Volcano28
Copy link
Copy Markdown

@Volcano28 Volcano28 commented Jan 18, 2026

Adds Gitea reminder bot:

Review reminder:

FPR (products/*): ping groups from BROKIN_REVIEW_PING_USERS

PR (pool/*): ping missing individual reviewers

Build reminder:

FPR (products/*): skip commenting on FPR itself; forward to referenced pool PR(s)

PR (pool/*): comment when ObsStaging is red

Anti-spam via markers: [REVIEW-REMINDER] and [OBS-STAGING-REMINDER]

Tested manually on:

pool/openldap2_6!7 (review reminder to the reviewer)

products/SLFO!1683 (group review reminder + forwarded build reminder)

@Firstyear
Copy link
Copy Markdown

Why are you pinging me on this random PR?

@Volcano28
Copy link
Copy Markdown
Author

Why are you pinging me on this random PR?

Hello, I apologize, I was testing the review bot in an one of the PR's that you were requested to review, and I mistakenly tagged your name, sorry about that, I removed it

@Firstyear
Copy link
Copy Markdown

So the intent is to make a new bot to spam me about a review that I can't complete? These reviews are currently all blocked.

@DimStar77
Copy link
Copy Markdown
Contributor

So the intent is to make a new bot to spam me about a review that I can't complete? These reviews are currently all blocked.

This seems to imply it's pinging too many / the wrong people

@Firstyear
Copy link
Copy Markdown

Firstyear commented Feb 4, 2026

So the intent is to make a new bot to spam me about a review that I can't complete? These reviews are currently all blocked.

This seems to imply it's pinging too many / the wrong people

My actual point is that the moment you even look at the new gitea workflow, you're gonna get so many notification you tune them all out.

There is actually a whole thing about notification fatigue, and how it causes incidents because people end up tuning out notifications meaning that legitimate notifications are ignored.

EDIT: In other words, even if you implement this bot, It's likely that I and others will ignore it. Don't try and make a new notification to fix a systemic problem.

@Volcano28
Copy link
Copy Markdown
Author

Volcano28 commented Feb 5, 2026

So the intent is to make a new bot to spam me about a review that I can't complete? These reviews are currently all blocked.

This seems to imply it's pinging too many / the wrong people

My actual point is that the moment you even look at the new gitea workflow, you're gonna get so many notification you tune them all out.

There is actually a whole thing about notification fatigue, and how it causes incidents because people end up tuning out notifications meaning that legitimate notifications are ignored.

EDIT: In other words, even if you implement this bot, It's likely that I and others will ignore it. Don't try and make a new notification to fix a systemic problem.

Thank you for your input. With the latest updates, We only notify the right FPR's for reviews. Only if the PR has the Label Staging/In Progress, will be reminded and send notifications. So there won't be any pinging for the PR's to the many or wrong people.

image

You can see here an example, These are only the necessary people listed in the FPR.

@Firstyear
Copy link
Copy Markdown

Thank you for your input. With the latest updates, We only notify the right FPR's for reviews. Only if the PR has the Label Staging/In Progress, will be reminded and send notifications. So there won't be any pinging for the PR's to the many or wrong people.
image

You can see here an example, These are only the necessary people listed in the FPR.

You're missing the bigger picture.

The point is not that this notification only happens once.

The point is that there are so many useless notifications coming out all the time that this notification will be missed in between all the junk.

Screenshot 2026-02-06 at 10 34 36

This one issue alone has sent me 8 emails. I have a few more that have even more. It seems if you even so much as look at gitea, that gitea stares back into your soul and begins to unless a torrent of email noise into your inbox.

Because of this your "just one more notification bro" will be lost in the sea of noise that already exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants