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
| PORT | Where the HTTP server should listen. | No |`8080`|
66
-
| STREAMLABS_TOKEN | A token to use the StreamLabs API. You can get one by using [StreamDevs/streamlabs-token](https://github.com/streamdevs/streamlabs-token)|**Yes**|_empty_|
67
-
| TWITCH_BOT_NAME | The account (username) that the chatbot uses to send chat messages. |**Yes**|_empty_|
68
-
| TWITCH_BOT_TOKEN | The token to authenticate your chatbot. Generate this with https://twitchapps.com/tmi/, while logged in to your chatbot account. The token will be an alphanumeric string. |**Yes**|_empty_|
69
-
| TWITCH_BOT_CHANNEL | The Twitch channel name where you want to run the bot. Usually this is your main Twitch account. |**Yes**|_empty_|
70
-
| NOTIFY_ISSUES_ASSIGNED_TO | A comma-separated list of GitHub user names. Only issues assigned to these users will be notified or leave it empty to receive all notifications. |**No**|_empty array_|
71
-
| IGNORE_PR_OPENED_BY | A comma-separated list of GitHub user names. Only PR not opened by these users will be notified or leave it empty to receive all notifications. |**No**|_empty array_|
72
-
| NOTIFY_CHECK_RUNS_FOR | Comma-separated list of branches to notify Check Runs for. Leave empty to notify for any branch |**No**|_empty__array_|
73
-
74
-
## How to configure the webhook in GitHub
75
-
76
-
### For sponsorships
98
+
| STREAMLABS_TOKEN | A token to use the StreamLabs API. You can get one by using [StreamDevs/streamlabs-token](https://github.com/streamdevs/streamlabs-token)| No |_empty_|
99
+
| TWITCH_BOT_NAME | The account (username) that the chatbot uses to send chat messages. | No |_empty_|
100
+
| TWITCH_BOT_TOKEN | The token to authenticate your chatbot. Generate this with https://twitchapps.com/tmi/, while logged in to your chatbot account. The token will be an alphanumeric string. | No |_empty_|
101
+
| TWITCH_BOT_CHANNEL | The Twitch channel name where you want to run the bot. Usually this is your main Twitch account. | No |_empty_|
102
+
| NOTIFY_ISSUES_ASSIGNED_TO | A comma-separated list of GitHub user names. Only issues assigned to these users will be notified or leave it empty to receive all notifications. | No |_empty array_|
103
+
| IGNORE_PR_OPENED_BY | A comma-separated list of GitHub user names. Only PR not opened by these users will be notified or leave it empty to receive all notifications. | No |_empty array_|
104
+
| NOTIFY_CHECK_RUNS_FOR | Comma-separated list of branches to notify Check Runs for. Leave empty to notify for any branch | No |_empty__array_|
105
+
106
+
### GitHub Configuration
107
+
108
+
#### Repositories
109
+
110
+
0. Open your repository settings on GitHub.
111
+
1. Go to the **Webhooks** section.
112
+
2. Click on **Add webhook**.
113
+
3. On the **Payload** field, enter the GitHub endpoint for your deployed webhook. For example `https://YOUR-SITE-HERE.herokuapp.com/github`.
114
+
4. For **Content type** we want to select `application/json`.
115
+
5. On **Which events would you like to trigger this webhook?** select `Let me select individual events`.
116
+
6. On the list of events check the following:
117
+
- Check runs
118
+
- Forks
119
+
- Issues
120
+
- Pull requests
121
+
- Releases
122
+
- Stars
123
+
7. Make sure the `Active` checkbox is checked
124
+
8. Click on `Add webhook`
125
+
9. You will receive your first notification on Twitch Chat and StreamLabs letting you now your webhook has been configured correctly.
126
+
127
+
#### Sponsorships
77
128
78
129
[Check the GitHub documentation](https://help.github.com/en/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)
79
130
@@ -89,7 +140,7 @@ Everyone is welcome to contribute to this repository. To do so follow these step
89
140
90
141
### Deploying to Heroku
91
142
92
-
You can use the "[deploy to Heroku](#webhook)" button link at the top of this readme file or use the Heroku CLI
143
+
You can use the "[deploy to Heroku](#deploy-to-heroku)" button or use the Heroku CLI
93
144
94
145
### Configuring your local repo to deploy on Heroku
0 commit comments