CI: remove unsupported max_errors arg from package check#71
Closed
Copilot wants to merge 3 commits into
Closed
Conversation
Copilot
AI
changed the title
[WIP] Fix failing CI job for pull request #70
CI: remove unsupported May 30, 2026
max_errors arg from package check
gforge
approved these changes
May 30, 2026
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
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.
The PR workflow was failing before package checks executed because
devtools::check(max_errors = 5)is incompatible with the CI toolchain (unused argument (max_errors = 5)). This change restores check-step compatibility while preserving current CI flow.Problem
Check packagestep in.github/workflows/ci.yamlpassed an unsupported argument throughdevtools::check.Change
Check packagecommand to use the supported invocation.Patch
Original prompt
This pull request was created from Copilot chat.