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
Distinguish the bot's name on GitHub and on each GitLab instance.
Introduce ppx_expect test for new function.
Co-authored-by: Erik Martin-Dorel <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+16-6Lines changed: 16 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -253,14 +253,21 @@ Once you finish the installation, follow these steps:
253
253
By default, **@coqbot** considers that both GitHub and GitLab repositories
254
254
share the same URL except for the "lab" replacing the "hub" part. If
255
255
that is not the case, assuming you created a GitLab repository whose
256
-
URL is <https://gitlab.com/owner/repo/>, add a file `coqbot.toml` at
256
+
URL is <https://mygitlab.example.com/owner/repo/>, add a file `coqbot.toml` at
257
257
the root of your GitHub repository and in its default branch (most often
258
258
named `master`), containing:
259
259
```
260
260
[mapping]
261
261
gitlab = "owner/repo"
262
+
gitlab_domain = "mygitlab.example.com"
262
263
```
263
-
If you use other instance of **@coqbot**, this repository-specific
264
+
If omitted, the `gitlab_domain` value defaults to `"gitlab.com"`.
265
+
Note that the value of `gitlab_domain` must be a supported GitLab
266
+
instance, i.e., it needs to be defined in the bot's own configuration
267
+
file (check [coqbot-config.toml](coqbot-config.toml) for the coqbot
268
+
instance configuration).
269
+
270
+
If you use another instance of **@coqbot**, this repository-specific
264
271
configuration file becomes `BOT_NAME.toml` where `BOT_NAME` is the name
265
272
of the bot.
266
273
@@ -345,11 +352,14 @@ to [Heroku](https://www.heroku.com/). Simply follow the official
345
352
The bot will need to read a few environment variables so make sure
346
353
these are configured in your Heroku app:
347
354
348
-
- `GITLAB_ACCESS_TOKEN`
349
-
- `GITHUB_ACCESS_TOKEN`
350
-
- `GITHUB_WEBHOOK_SECRET`
355
+
- `GITHUB_ACCESS_TOKEN`(can also be defined in the configuration file as `github.api_token`)
356
+
- `GITLAB_ACCESS_TOKEN`(can also be defined for each GitLab instance through the configuration file as `api_token` or through an environment variable whose name is defined in the configuration file as `api_token_env_var`)
357
+
- `GITHUB_WEBHOOK_SECRET`(can also be defined in the configuration file as `github.webhook_secret`)
358
+
- `GITLAB_WEBHOOK_SECRET`(can also be defined in the configuration file as `gitlab.webhook_secret`, will default to `GITHUB_WEBHOOK_SECRET` if not defined)
359
+
- `DAILY_SCHEDULE_SECRET`(can also be defined in the configuration file as `github.daily_schedule_secret`, will default to `GITHUB_WEBHOOK_SECRET` if not defined)
360
+
- `GITHUB_APP_ID`(can also be defined in the configuration file as `github.app_id`)
351
361
- `GITHUB_PRIVATE_KEY`(a private key of your GitHub app)
352
-
- `GITHUB_APP_ID`(your GitHub App ID)
362
+
- `PORT`(can also be defined in the configuration file as `server.port`)
353
363
354
364
Then, you must configure the bot with a configuration file. Here is an example
355
365
to adapt to your needs [`example-config.toml`](example-config.toml)).
0 commit comments