Milestones
List view
**Goal** Make the bot fully configuration-driven. Repo-specific behavior is read from `coqbot-config.toml`; onboarding a new repo should not require source changes. **Status** Done: - M1 Config schema + parser - https://github.com/rocq-prover/bot/pull/371 - M2 Backport / project cards - https://github.com/rocq-prover/bot/pull/376 In review: - M5 CI job dispatch + doc status - https://github.com/rocq-prover/bot/pull/377 - M6 PR sync, team checks, command gating - https://github.com/rocq-prover/bot/pull/378 - M4 Bench GitLab job URLs - https://github.com/rocq-prover/bot/pull/379 - M7 Minimizer URL - https://github.com/rocq-prover/bot/pull/380 **Milestone details** **M1 — Config schema + parser** (done) Files: `src/config/repo_config.ml`, `coqbot-config.toml`, tests - Per-repo TOML schema, lookup helpers, `find_by_github` **M2 — Backport / project cards** (done) Files: `src/actions/backport.ml`, `src/webhooks/github.ml` (project events) - Backport and GitHub project card logic from config **M5 - CI job dispatch + doc status** PR: https://github.com/rocq-prover/bot/pull/377 Files: `src/actions/job.ml`, `src/ci/documentation.ml`, `src/ci/job_status.ml`, `src/webhooks/gitlab.ml` Depends on: M1 - Route bench jobs and Rocq-specific failure handling from `repo_config.jobs` - Doc artifact / GitLab status URLs from GitLab coordinates; gate on `doc_artifact_jobs` - Thread `repo_config_table` through the GitLab job webhook **M6 - PR sync, team checks, and command gating** PR: https://github.com/rocq-prover/bot/pull/378 Files: `src/actions/pr_sync.ml`, `src/webhooks/github.ml` (`handle_comment_created`), `src/utils/bench.ml` (org/team/domain args), `bot-components/github/GitHub_automation.ml`, `src/config/repo_config.ml` Depends on: M1 - Welcome message gated on `contributing_url` (absent -> skip) - Team mentions and merge/run-ci authorization from `org_name` + `teams` + `alert_mention` - `run ci`, `merge now`, `bench` accepted when repo has the relevant config/team (no `rocq-prover/rocq` guard) - `run_ci_action` / `run_bench` take org/team/gitlab_domain from config **M4 - Bench GitLab job URLs** PR: https://github.com/rocq-prover/bot/pull/379 Files: `src/utils/bench.ml`, `src/webhooks/github.ml`, `src/webhooks/gitlab.ml` Depends on: M1 - Build status job URL from `gitlab_domain` / `gitlab_owner` / `gitlab_repo` - Build bench-summary job-link regex from the same coordinates + `bench_job` - Tests: URL/regex from config; missing GitLab coords handled cleanly **M7- Minimizer URL** PR: https://github.com/rocq-prover/bot/pull/380 Files: `src/webhooks/github.ml`, `src/ci/minimization.ml`, `src/webhooks/gitlab.ml` Depends on: M1 - Use `repo_config.minimizer_url`; skip minimization offer when absent - Tests: with URL -> link present; without -> absent **M3 - Push / mirror routing** PR: https://github.com/rocq-prover/bot/pull/381 Files: `src/webhooks/github.ml` (`handle_push_event_for_repos`, push branches) Depends on: M1 - Replace owner/repo string-match chains with `repo_config` lookups - Push on configured repo: backport if project configured; mirror if GitLab mapping exists - Tests: configured push mirrors; unconfigured push is a no-op **M8 - Integration test + example config** Depends on: M3–M7 (and merged M5/M6) - End-to-end test with two repos in TOML + synthetic webhooks - Add `docs/example-config.toml` - Remove any remaining dead hardcode paths
No due date•3/8 issues closedNote: **We can propose this as a topic for a Master’s internship** ([draft proposal](https://github.com/rocq-prover/bot/blob/quyen%40proposal_ocaml5/internship_proposal_m2.md)) LWT is currently used throughout the codebase for HTTP requests (Cohttp_lwt), Git operations (Lwt_process, Lwt_io), GraphQL queries, webhook handling, and all I/O operations. OCaml 5 introduces effect handlers that enable direct-style concurrency without monads. The main alternative to LWT is **Eio** (Effect-based I/O), which provides non-local control flow, direct-style code (no monadic bind operators), and fiber-based concurrency similar to async/await. **Risks**: - This will touch nearly every file - HTTP and webhook handling are ciritcal - Eio's ecosystem is still maturing # Migration plan **LWT -> Eio** - `Cohttp_lwt` -> `piaf` or `cohttp-eio` - `Lwt_process` -> `eio.process` - `Lwt_io` -> `eio.flow` - ... ## Migrate strategy One module at a time, complete with test passed. We can try the `Lwt_eio` approach, which allows running [Lwt code](https://github.com/ocaml-multicore/lwt_eio) from within Eio.
No due date