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
Copy file name to clipboardExpand all lines: docs/execution-model.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,6 +56,7 @@ The table below lists supported explicit triggers, categorized into those enable
56
56
| :fontawesome-brands-github: Transition from draft to ready for review |`pr_ready_for_review`|`off`|
57
57
| :fontawesome-brands-github: transition from any state to closed |`pr_closed`|`off`|
58
58
| :fontawesome-brands-github: transition from closed to open |`pr_reopened`|`off`|
59
+
| :fontawesome-brands-github: Approving the PR |`pr_approved`|`off`|
59
60
60
61
Explicit triggers are set independently per each automation block and can be configured at the file level, specific to each automation separately or in combination. If triggers are listed at the file level **and** specific automation, the automation will be triggered according to both triggers.
61
62
If an automation block does not have explicit triggers configured, it will be triggered according to the default (implicit) triggers.
0 commit comments