Can I suppress VCS messages in Push policies for tracked commits?

Currently, Spacelift does not support suppressing VCS (Version Control System) messages directly within Push policies using Rego code.

Why `message = false` doesn't work

You cannot use message = false in your Push policy to disable GitHub PR feedback because:

• message is a reserved rule in the Spacelift Rego policy framework

• The message rule must be a string, not a boolean value

• Setting it to false will result in a parsing error: "conflicting rules data.spacelift.message found"

Current limitations

The notify rule (which is false by default) only applies to ignored pushes and cannot be set to false to silence commit status checks for proposed runs.

This means there is currently no direct mechanism to completely silence GitHub status updates in a Push policy when using the "track but do not run" approach.

Workaround considerations

If you're using the "track but do not run" policy and triggering runs via API afterward, you will currently receive duplicate notifications on the VCS side (such as GitHub PR comments). This is expected behavior with the current implementation.

Request this feature

If suppressing VCS messages for tracked commits is important for your workflow, consider submitting a feature request through the Spacelift feedback portal. This allows the community to upvote the idea and helps the product team prioritize features based on demand.