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
{{ message }}
This repository has been archived by the owner on Apr 30, 2023. It is now read-only.
Hey, thank you for creating this github action, it really helps us with our deployment flow. We are, however, not able to get the actions_comment flag to work, would you mind helping us with it?
In our yaml file we are setting the permissions:
permissions:
contents: writepull-requests: write
And then we use the following (AWS credentials are available via env variables):
This creates a diff for the two stacks we have and prints out the differences (the first one has differences, the second ones doesn't), but no message is written to the PR. Could it be that it works only with one stack at a time?
Stack stack-name-1
IAM Statement Changes
[...]
Resources
[+] AWS::Events::Rule [..]
Stack stack-name-2
There were no differences
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey, thank you for creating this github action, it really helps us with our deployment flow. We are, however, not able to get the
actions_comment
flag to work, would you mind helping us with it?In our yaml file we are setting the permissions:
And then we use the following (AWS credentials are available via env variables):
This creates a diff for the two stacks we have and prints out the differences (the first one has differences, the second ones doesn't), but no message is written to the PR. Could it be that it works only with one stack at a time?
The text was updated successfully, but these errors were encountered: