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
+3-46Lines changed: 3 additions & 46 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -196,25 +196,6 @@ you are interested in hearing about it.
196
196
197
197
## How to use the **@coqbot** instance ##
198
198
199
-
### As a GitHub App
200
-
201
-
This is the recommended installation method, as this is both easier to
202
-
set up and it gives access to new features (related to GitHub Checks).
203
-
204
-
Notes:
205
-
206
-
- Installation as a GitHub App is still in an experimental stage
207
-
and you may frequently receive requests to expand permissions.
208
-
209
-
- All the repositories that use the bot and belong to the same
210
-
owner must install the bot using the same method (GitHub App or
211
-
regular user).
212
-
213
-
- If you were previously using the legacy installation method,
214
-
make sure you disable any previously set up GitHub webhooks when
215
-
switching to the GitHub App, otherwise the bot will receive every
216
-
request twice.
217
-
218
199
The bot can be installed as a GitHub App to either your account or
219
200
organization ([link to app](https://github.com/apps/coqbot-app)).
220
201
Once you finish the installation, follow these steps:
@@ -271,32 +252,6 @@ Once you finish the installation, follow these steps:
271
252
configuration file becomes `BOT_NAME.toml` where `BOT_NAME` is the name
272
253
of the bot.
273
254
274
-
### As a regular user account (legacy)
275
-
276
-
The bot used to be given access to each of your GitHub repositories as a
277
-
regular GitHub user account (**@coqbot**). This installation method is
278
-
still supported for repositories that haven't migrated to the GitHub App
279
-
yet. Here are the steps to follow in addition to those described in the
280
-
`As GitHub App` section:
281
-
282
-
- In your GitHub repository:
283
-
284
-
- go to "Settings" / "Manage access" to add
285
-
[**@coqbot**](https://github.com/coqbot) as a collaborator with
286
-
the "Write" role (so that it can push status checks, and set
287
-
labels).
288
-
289
-
Currently, every invitation requires a manual validation, so there
290
-
may be some lag before **@coqbot** can push status checks
291
-
to your repository.
292
-
293
-
- go to "Settings" / "Webhooks" and add one webhook with URL
294
-
<https://coqbot.herokuapp.com/github> that will only be triggered
295
-
at least by pull request events, and if you want to use the issue
296
-
milestone feature, by issue events as well. Make sure you change
297
-
the "content/type" value to "application/json".
298
-
299
-
300
255
301
256
## Architecture ##
302
257
@@ -352,14 +307,16 @@ to [Heroku](https://www.heroku.com/). Simply follow the official
352
307
The bot will need to read a few environment variables so make sure
353
308
these are configured in your Heroku app:
354
309
355
-
- `GITHUB_ACCESS_TOKEN`(can also be defined in the configuration file as `github.api_token`)
356
310
- `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
311
- `GITHUB_WEBHOOK_SECRET`(can also be defined in the configuration file as `github.webhook_secret`)
358
312
- `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
313
- `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
314
- `GITHUB_APP_ID`(can also be defined in the configuration file as `github.app_id`)
361
315
- `GITHUB_PRIVATE_KEY`(a private key of your GitHub app)
362
316
- `PORT`(can also be defined in the configuration file as `server.port`)
317
+
- (optional) `GITHUB_ACCESS_TOKEN` / `github.api_token` in config: only needed
318
+
for Rocq minimization flows that must act as the `coqbot` user rather than
319
+
the GitHub App
363
320
364
321
Then, you must configure the bot with a configuration file. Here is an example
365
322
to adapt to your needs [`example-config.toml`](example-config.toml).
0 commit comments