Skip to content
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

Posting errors could be improved #22

Open
notgne2 opened this issue Jan 11, 2023 · 0 comments
Open

Posting errors could be improved #22

notgne2 opened this issue Jan 11, 2023 · 0 comments

Comments

@notgne2
Copy link
Contributor

notgne2 commented Jan 11, 2023

Every now and then one of these pops up serokell/deploy-rs#152 and can at times get quickly filled with many "similar" comments, meaning GitHub won't even show you what the latest error is. This also means by the time I can unsubscribe from the thread I now have multiple notifications instead of just one.

image

I think it would be better just to edit the issue message with whatever the current error is, rather than appending to an ever expanding list of errors. For PRs that become error-y, it can instead post a single error comment and update it (maybe post a new one if the last comment is by somebody else)

It also looks like error issues do not get closed out, as serokell/deploy-rs#187 still exists despite serokell/deploy-rs#189 now having been created.

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

No branches or pull requests

1 participant