Add the OCaml problem matchers
Open
Nobody has claimed this yet.
enhancement
help wanted
upstream
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 48
- Avg merge
- 15m
- Merged PRs (30d)
- 10
Description
Can probably get these from the VSCode plugin, but need to check that they work with the OCaml 4.08+ new error message format.
Contributor guide
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 inspecting the GitHub Action's existing problem matcher configuration and comparing it with the VSCode plugin's OCaml matcher definitions. Verify the patterns against the OCaml 4.08+ error message format; done means OCaml diagnostics are matched correctly by the action.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, ocaml, vscode
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100