Skip to main content

Default notification policy should post a comment about the failed action

Feature RequestsIaC WorkflowsVCSPolicies

When a PR stack run fails, there is no notification of the failure posted back to the pull request. The status check or pipeline is marked as failed, but I’m usually watching the PR comments or my email for a notification of the run status.

It would be great if the default notification policy were updated to post a comment about a failed run back to the PR.

Workaround
Custom notification policy
Problem
Status: ❌ Rejected2 comments

Log in to comment and vote

Comments2

  • Black Breeze

    •

    Nov 19, 2025

    I wanted to provide a closure here. We discussed it as a team and did some discovery across the user base. The consensus is that the current consensus strikes the right balance between signal and noise for most users. The power of the policy-as-code engine is that the default policy can be easily modified by anyone whose needs and processes are better served by more a verbose notification system. If the learning curve for the required Rego changes are too steep, please reach out to us and our Solutions team is happy to assist.

  • Beige Celestial

    •

    Sep 3, 2025

    This would be more useful rather than click-ops through the run to find the cause of failure.
    Worst case this could be a setting for the instance or stack to enable or disable.