OCaml bot for GitHub interactions
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 42
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
There have been a few requests in recent years for a more "active" bot for various repository actions to be triggered via a GitHub comment. The current requests are:
- for opam-repository maintainers to have more control over whether certain expensive tests are run, for example reverse dependencies on popular packages like
dunethat trigger a lot of builds. - for benchmarking infrastructure to trigger off tests. This is being discussed in https://github.com/coq/bot/issues/288
- for package releases to be generated and tested ahead of a submission to opam-repository.
There are a couple of workflow mechanisms we can use for this, possibly in combination:
- the Coq project has https://github.com/coq/bot
- the Ocurrent project has reactive webhooks from GitHub https://github.com/ocurrent/overview
We already have several GitHub bot accounts that are suitable for use as a host for this: @bactrian and @vicuna.
This is a tracking issue for the deployment and maintainence of such a bot once the prototypes have been completed.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing Coq bot and Ocurrent webhook approaches linked in the issue, along with the requested opam-repository, benchmarking, and package-release workflows. Define the deployment and maintenance plan for a bot hosted by @bactrian or @vicuna; the work is done when the selected prototypes are deployed and the requested comment-triggered actions are supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, ocaml
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100