Using ci-cargo from extendr
#55
Merged
Conversation
This file contains hidden or 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
clauswilke
approved these changes
May 4, 2021
CGMossa
pushed a commit
to CGMossa/libR-sys
that referenced
this pull request
Jan 21, 2024
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.
In light of the new release of Rtools (Rtools40v2, see discussion here #21), which allows us to finally fix Rtools bindgen tests, I suggest to slightly improve the CI, reducing the amount of boilerplate.
This was previously done in
extendrby introducingci-cargo.ps1powershell script that handlescargoerrors in a cross-platform manner.I took
ci-cargo.ps1fromextendrand replaced all boilerplate code with simple calls toci-cargo.