Add a trunk-build github action #501
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds an action that builds with the latest supported trunk. I heavily reused the work of @shym from ocaml-ppx#410, thank you for this contribution! Signed-off-by: Nathan Rebours <[email protected]>
NathanReb
requested review from
ceastlund,
panglesd,
patricoferris and
pitag-ha
as code owners
NathanReb
added
the
no changelog
|
The trunk build fails atm of course because our opam bounds don't allow for OCaml 5.3. |
patricoferris
approved these changes
Jun 14, 2024
Signed-off-by: Nathan Rebours <[email protected]>
shym
approved these changes
Jun 17, 2024
Signed-off-by: Nathan Rebours <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds an action that builds with the latest supported trunk. We'll need this for incremental trunk support and I'd like to see it run on #487.
I heavily reused the work of @shym from #410, thank you for this contribution!