-
Notifications
You must be signed in to change notification settings - Fork 0
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
Thank you for forking TF-via-PR! #1
Conversation
Hi, awesome project btw! There was an issue with 'on-change' not working because my terraform install had the github actions "wrapper" enabled. Also, there's a case where with |
Thanks for the kinds words!
Ooh, I wasn't aware the
Ooh, that's a great edge-case which I hadn't considered! Did you manage to make this work as expected on your fork? |
By the way, you're likely one of the first adopters of the |
I believe the exitcode is always 0 with the wrapper so the exitcode/comment logic wouldn't work.
I think so, I haven't actually ran into it lately.
Works great! Another thing I realized is very large plans may run into github comment length limit. |
Ooh, that's a great call-out — I'll have to document it in the README.
Thankfully, that shouldn't be an issue since the Action truncates to fit well within GitHub's comment's limit (2e16 = 65,536) automatically! |
Yeah it still posts a comment, but the plan itself is then not fully visible |
That's right, the plan isn't fully visible in the PR comment due to GitHub's character limit restrictions. However, if you click the "view log" link in the footer, it should redirect you to the exact workflow > job > step, where the plan is available in its entirety. Here's an example of a PR comment with a truncated plan. Lemme know how that works out for you! |
Oh I see, that should be fine then. |
Happy to share this has been shipped with v13.1.0, where your contribution has been credited! Please consider ⭐ this project, if you or your team find it useful. @ctian1 Not only has |
Hey @ctian1, thanks for the fork, and great to see a flurry of activity around PR-commenting logic!
Is there any particular feature or enhancement you're looking for? Happy to help support 👍