Rule Triggers define when the rule is evaluated. They determine which event wakes up the Process Guardian and starts the rule evaluation, for example when a pull request is created, updated, or when another supported workflow event occurs.
|
Trigger |
Description |
Status |
|---|---|---|
|
Commit |
Evaluates the rule when a commit is created. This ensures that compliance checks are applied directly to individual commits. |
Release 2026 |
|
Push |
Evaluates the rule when changes are pushed to the repository. This allows validation of multiple commits as part of a push operation. |
Release 2026 |
|
Pull request |
Evaluates the rule when a pull request is created or updated. This ensures that compliance requirements are checked before changes are reviewed or merged. |
Release 2026 |
|
Merge commit |
Evaluates the rule when a merge commit is created via Pull Request. This ensures that the final integration commit meets all compliance requirements. |
Plan 2026 |
Server-side push validation will become available once Atlassian provides the necessary API support. Currently, push validation can only be implemented through client-side integrations such as local Git hooks or CI/CD pipelines. Commit and push validation