You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Describe the user story
The communication with Atlantis is very spamming. On a Pull Requests It results into a lot of comments which generates a lot of notifications of assigned reviewer. Especially, if the first try wont work, it would result into more unnecessary comments.
Describe the solution you'd like
Like #2818, Atlantis should own only comment if possible. The communication with Atlantis should be done via checkboxes.
Describe the drawbacks of your solution
Larger plans/outputs does not fit into one comments, consider to attach them as file attachment.
I think having it post a comment is reasonable if it can support updating the same comment.
IMO the spam problem is due to each push creating and posting new plans. I mean if they were not applied why do I care about them? the current plan is what's important.
Community Note
Describe the user story
The communication with Atlantis is very spamming. On a Pull Requests It results into a lot of comments which generates a lot of notifications of assigned reviewer. Especially, if the first try wont work, it would result into more unnecessary comments.
Describe the solution you'd like
Like #2818, Atlantis should own only comment if possible. The communication with Atlantis should be done via checkboxes.
Describe the drawbacks of your solution
Larger plans/outputs does not fit into one comments, consider to attach them as file attachment.
Describe alternatives you've considered
Use the check run API to publish the outputs (https://docs.github.com/en/rest/guides/using-the-rest-api-to-interact-with-checks?apiVersion=2022-11-28)
The text was updated successfully, but these errors were encountered: