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.
I have dozens of Atlantis servers running (one per cloud account) and in some cases, the Terraform change has to be processed by all of them. This causes a lot of comment noise in the GitHub PR thread. I would like to rely solely on the GitHub status checks in those cases.
Describe the solution you'd like
It would be helpful to have an ENV VAR like ATLANTIS_SILENCE_COMMENTS=true (or something more flexible e.g. ATLANTIS_SILENCE_COMMENTS=plan,apply, ATLANTIS_SILENCE_COMMENTS=all), which could be set globally or per workflow step to stop Atlantis from posting comments to the GH PR thread, but leave the GH status_check behavior unchanged.
Describe the drawbacks of your solution
None.
Describe alternatives you've considered
Tried using the workflow step run command output: hide option. It disables the Terraform output but the minimal comment with the atlantis apply|unlock instructions is still posted to GH PR thread.
The text was updated successfully, but these errors were encountered:
Community Note
Describe the user story
I have dozens of Atlantis servers running (one per cloud account) and in some cases, the Terraform change has to be processed by all of them. This causes a lot of comment noise in the GitHub PR thread. I would like to rely solely on the GitHub status checks in those cases.
Describe the solution you'd like
It would be helpful to have an ENV VAR like
ATLANTIS_SILENCE_COMMENTS=true
(or something more flexible e.g.ATLANTIS_SILENCE_COMMENTS=plan,apply
,ATLANTIS_SILENCE_COMMENTS=all
), which could be set globally or per workflow step to stop Atlantis from posting comments to the GH PR thread, but leave the GH status_check behavior unchanged.Describe the drawbacks of your solution
None.
Describe alternatives you've considered
Tried using the workflow step
run
commandoutput: hide
option. It disables the Terraform output but the minimal comment with theatlantis apply|unlock
instructions is still posted to GH PR thread.The text was updated successfully, but these errors were encountered: