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: integrations/github/workflows/ReadMe.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,3 +51,30 @@
51
51
### Step 5. Congratulations! You now know how to create and run browser tests with GitHub Actions/Workflows!
52
52
53
53
### **Study [SeleniumBase](https://github.com/seleniumbase/SeleniumBase) to learn more!**
54
+
55
+
56
+
### Slack notifications:
57
+
* the action [rtCamp/action-slack-notify](https://github.com/rtCamp/action-slack-notify) is just one of the many slack notification actions available
58
+
* create a slack integration webhook if you don't have one already
59
+
* create a `SLACK_WEBHOOK` secret on your repository with the webhook token value
60
+
* for this particular action, `SLACK_CHANNEL` is optional environment variable and will default to the webhook token channel if not specified
61
+
* this example shows how you can put a link to your workflow as the `SLACK_MESSAGE` (good to see artifacts pushed up such as from the SeleniumBase presenter feature!)
### Upload a SeleniumBase presentation as an artifact
74
+
* Here is an example how to use [upload-artifact@v2](https://github.com/actions/upload-artifact) to push up a SeleniumBase generated presentation as an artifact. (You can use this in conjunction with the Slack notification to grab and or view the presentation directly from github)
75
+
```
76
+
- uses: actions/upload-artifact@v2
77
+
with:
78
+
name: Click here to download SeleniumBase presentation!
0 commit comments