-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please reduce the amount of comment packit sends to src.fp.o Pull Requests #2230
Comments
hi @hroncok ! Thank you for bringing up this issue. Regarding the decision to create a dedicated comment for each syncing, our intention was to maintain transparency, considering that a retriggered sync has a new dashboard link. This approach ensures that each comment corresponds to a specific run and shows the time of it, making it easier to trace the history of syncs. But I understand the issue regarding the potential noise it creates. We could change the behaviour to include the link in the PR description and for retriggers overwrite it or just provide list of links (or creating the additional comments only for retriggered syncs?) We will discuss this with the team on Monday and provide an update here. |
Comments for retriggers are probably fine. They provide valuable feedback that it happened. I only suggest to fold the firts comment to the pr description. |
Don't comment about logs on just submitted sync PR Fixes packit/packit#2230 RELEASE NOTES BEGIN We have adjusted commenting behaviour regarding Packit logs on release syncing PRs. RELEASE NOTES END Reviewed-by: Maja Massarini Reviewed-by: Laura Barcziová
What happened? What is the problem?
In January, I received 69 emails from src.fp.o generated by the packet user.
In December it was 110.
As more and more packagers embrace packit, I get more and more emails (mostly from packages co-maintained by python-packagers-sig).
Every Pull Request opened by packit almost immediately receives a comment by packit, doubling the amount of email notifications.
Please consider folding the initial comment to the PR description.
Thanks.
What did you expect to happen?
No immediate comments by packit on packit PRs.
Example URL(s)
https://src.fedoraproject.org/rpms/python-PyGithub/pull-request/26#comment-181891
Steps to reproduce
1. Be subscribed to notifications for many packages that use packit. 2. Receive hundreds of email from src.fp.o by packit. 3. Miss important email from PRs opened by humans because they are easy to miss.
Workaround
Participation
The text was updated successfully, but these errors were encountered: