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.
Overview of the Issue
Since the GitHub REST API ListComments endpoint doesn't expose the isMinimized attribute, on each Atlantis command, we sequentially minimize Atlantis comments, even if they are already minimized. This process can take significant time, proportional to the number of existing Atlantis comments within a pull request.
We might consider switching to the GitHub GraphQL API for listing comments, as it exposes the isMinimized attribute. This would help avoid performance degradation by minimizing only the last Atlantis comment, as opposed to processing all comments sequentially.
Community Note
Overview of the Issue
Since the GitHub REST API
ListComments
endpoint doesn't expose theisMinimized
attribute, on each Atlantis command, we sequentially minimize Atlantis comments, even if they are already minimized. This process can take significant time, proportional to the number of existing Atlantis comments within a pull request.We might consider switching to the GitHub GraphQL API for listing comments, as it exposes the
isMinimized
attribute. This would help avoid performance degradation by minimizing only the last Atlantis comment, as opposed to processing all comments sequentially.Relevant code is here
I'd like to work on the fix for this.
Reproduction Steps
Logs
Logs
The text was updated successfully, but these errors were encountered: