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: README.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,13 @@
6
6
## How it works
7
7
8
8
At the end of a workflow, on success() and on failure(), call this action with the current status as a parameter (success/failure).
9
+
10
+
### If notification-type = release
11
+
12
+
This action will send a release notification with the current status (success or failure) whatever the current and previous workflow status.
13
+
14
+
### If notification-type = on-state-change
15
+
9
16
This action will first check the previous workflow status and will send a Slack notification according to the current workflow status.
10
17
Status is retrieved from cache if the current workflow has already run previously (from `re-run all jobs` button for example).
11
18
If it's the first time this workflow runs, this action will retrieve previous workflow status on the same branch with `gh` cli using provided `github-token`.
@@ -22,6 +29,10 @@ It'll not send a notification to Slack if:
22
29
- Current status is `success` and it's the first run.
23
30
- Current status is `failure` and previous run status was `failure`.
24
31
32
+
### If notification-type = on-failure-and-recover
33
+
34
+
Same as on-state-change but will notify on each failure (so will also notify when current status is `failure` and previous run status was `failure`).
0 commit comments