pep/cusku
1
0
Fork 0
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity

Collate bursts of events #1

New issue
Open
opened 2024-08-30 18:05:06 +00:00 by pep · 0 comments
pep commented 2024-08-30 18:05:06 +00:00
Owner
Copy link

It happens that there are bursts of activity in the repo that causes many events to be received and displayed in the room, which can be very spammy.

Proposed solutions:

  • Wait for a few seconds (~10? configurable) and collate whatever events is caught during this time. Maybe we for $seconds more if there are more events during this window. Send all in bulk, maybe with text reworked so that it doesn't include all intermediary steps.
  • Edit the bot's messages as new events come if they concern the same issues/MR/etc.
  • Both at the same time.
It happens that there are bursts of activity in the repo that causes many events to be received and displayed in the room, which can be very spammy. Proposed solutions: - Wait for a few seconds (~10? configurable) and collate whatever events is caught during this time. Maybe we for $seconds more if there are more events during this window. Send all in bulk, maybe with text reworked so that it doesn't include all intermediary steps. - Edit the bot's messages as new events come if they concern the same issues/MR/etc. - Both at the same time.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
forgejo-hooks
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: pep/cusku#1
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?