-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
GHA: add a job that test plugins compilation #6394
base: master
Are you sure you want to change the base?
Conversation
test_project "ocaml-opam" "opam-publish" 0 "make" | ||
test_project "AltGr" "opam-bundle" 0 "make" | ||
test_project "ocamlpro" "opam-custom-install" 1 "dune build" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would also suggest adding dune-release
, odep
, odig
, odoc-driver
, opam-check-npm-deps
, opam-build
, opam-test
, opam-dune-lint
, opam-graph
, opam-package-upgrade
, orb
, opam-0install
and topkg-care
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was package to test (some are failing on purpose as they have a dependency on opam < 2.2, see commits message). We'll need to select what package to add here : they are blocking for the PR merge.
Ideally we would have another more light mechanism, one that sends the information as a comment in the PR for ex., like that we are aware without blocking the PR (for packages that we don't maintain).
In it based on the same mechanism than opam-rt, it permits to keep them synchronised with the current API