New
January 29, 2025
Introducing Ignored Run Warnings
We are proud to announce that Ignored Run Warnings are now live. These warnings will help you identify why a run has not been triggered when a commit is pushed to your repository. By visiting the main stack view, you will get a warning box that explains why the latest commit has been ignored in case your stack isn't in sync.
In the above example, this happened because no files in the project root were affected by the latest commit.
Other reasons why a commit might be ignored are:
- applied push policies dismiss the commit
- default push policy was disabled and there are no custom push policies applied
- a tag was pushed to the repository
- changes were made outside the project root defined in stack settings
You can see why certain runs were not triggered in the new Ignored runs tab. The retention period for this is 7 days.
Keep in mind that this feature is available from the Starter+ tier. We encourage your feedback so let us know what you think!