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
- name: Comment Terraform Plan results in PR and as job summary
uses: liatrio/[email protected]
with:
json-file: ${{ env.WORKING_DIR }}/tfplan.json
expand-comment: 'true'
include-plan-job-summary: 'true'
Actual behaviour:
During a pull request everything works fine. Comments are posted to PR and job summary as well.
But when I'm running workflow in a non-pull request, I'm receiving following warnings:
Warning: Action doesn't seem to be running in a PR workflow context.
Warning: Skipping comment creation.
Expected behaviour:
Because README says "When include-plan-job-summary = true, if the action is executed in non-Pull Request workflows, the plan output will also be posted to the job summary of that run. If you do not wish to have this behavior, apply conditional logic to your workflow file.", I expect posting results to job summary during non-pull request.
Thanks for your help,
Thomas
The text was updated successfully, but these errors were encountered:
@leuthelt This should be fixed in v1.6.0. The release notes on that version dont call out this bug being fixed as it was not in the title of the PR but the PR did address this issue and I tested it.
Hello,
I'm using below GitHub Workflow configuration:
Actual behaviour:
During a pull request everything works fine. Comments are posted to PR and job summary as well.
But when I'm running workflow in a non-pull request, I'm receiving following warnings:
Expected behaviour:
Because README says "When include-plan-job-summary = true, if the action is executed in non-Pull Request workflows, the plan output will also be posted to the job summary of that run. If you do not wish to have this behavior, apply conditional logic to your workflow file.", I expect posting results to job summary during non-pull request.
Thanks for your help,
Thomas
The text was updated successfully, but these errors were encountered: