Skip to content
Prev 62945 / 63424 Next

R CMD check and CRAN's Rust policy

I took a more extreme version of this approach for a project that keeps many R packages in a monorepo and checks them all at once, where we do a lot of saying ?let?s ignore this warning _in this package_ until someone has a chance to fix it properly, but still fail the build if it shows up in _other packages_?.

The key idea in our approach is for each package you check to cache a previous check result that contains the warning(s) you want to ignore, then compare the current check against it and have your action fail only on _newly added_ warnings.

My implementation[1] is brittle and fussy and could be simplified a lot if you?re only checking one package at a time, but may be a useful starting point.

[1] https://github.com/PecanProject/pecan/blob/develop/scripts/check_with_errors.R