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
By default, the notification links to the repository that triggers the job. You can overwrite that using the `repository` field, which is useful for managing the release for multiple repositories in one place. See [scribd-api-proto](https://github.com/scribd/scribd-api-proto) for example.
51
51
@@ -60,6 +60,17 @@ steps:
60
60
channel: test-release-notification
61
61
repository: scribd/scribd-api-ruby
62
62
```
63
+
Additionally, `status` can be set explicitly to `success`, `failure` or another custom value to override the default behavior of using status of the job calling this action.
64
+
65
+
```yaml
66
+
steps:
67
+
- name: Send notification
68
+
uses: scribd/job-notification@main
69
+
with:
70
+
token: ${{ secrets.SCRIBD_SLACK_GENERIC_TOKEN }}
71
+
channel: test-release-notification
72
+
status: warning
73
+
```
63
74
64
75
## Development
65
76
@@ -69,4 +80,4 @@ You can test your changes by pushing them to a branch, which will trigger the [t
0 commit comments