-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Feature Request: Support customized Atlantis comment responses #456
Comments
Maybe we can fix this in the existing comments since other users are probably having the same issues? What were you thinking to make it clearer? |
Actually, you know what would be really handy. A way to require To answer your question:
Maybe something like this?
|
How's that? Also, you might be interested in the upcoming automerge feature: #457 |
If #446 were implemented, an approach could be to prevent merging (using master branch protection) until after the apply status check has passed 😁 |
Even with automerge (which is now implemented), users could still merge the pull request before the apply is run. #446 would be the best solution. |
#514 splits webhooks between plan and apply. I'll leave it up to @lkysow if this issue should still remain open but #514 resolves my particular reasoning for custom messages. It might still be nice to allow the output of scripts run in custom workflows to be part of Atlantis comments but I'm not sure I know how this would be done without just allowing stdout to flow through to the PR comment (which could be ugly). |
Custom scripts output does show up in the comments. |
Sounds like this issue can be resolved then. Thanks for all the work! |
Well this request is originally for "Feature Request: Support customized Atlantis comment responses" so none of those tickets is really related. But if k4k doesn't need this feature anymore then I don't think it's a problem that the issue is closed. |
atlantis apply |
We allow users to perform their own apply/merge on changes with Atlantis after code owner approval of a PR. The message from Atlantis is slightly unclear as to the order of operations which has led more than one user to merge a PR before running
atlantis apply
and requires that a "dummy" PR for the same commit be opened and then closed without merging to trick Atlantis in to running the apply. It would be really nice if either we could provide clarity on this in the standard auto-plan message or if Atlantis supported an easy way to customize auto-plan messages.The text was updated successfully, but these errors were encountered: