You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given that this package doesn't have any dependencies on other RMI-PACTA repos (either as "hard" Imports, or "soft" Suggests), running R CMD CHECK with the dev versions of r2dii.match and .analysis doesn't make much sense, since there isn't anything called from those repos.
Can anyone think of a reason to keep this check in here? @RMI-PACTA/r-developers
Context: I'm planning to ensure checks against dev-versions of dependencies in .match (RMI-PACTA/r2dii.match#480) .analysis (RMI-PACTA/r2dii.analysis#501) and .plot (RMI-PACTA/r2dii.plot#567) which captures the "upstream" direction, but do we need to capture "downstream" for some reason (if we're not executing any of that code)
Given that this package doesn't have any dependencies on other RMI-PACTA repos (either as "hard"
Imports
, or "soft"Suggests
), running R CMD CHECK with the dev versions ofr2dii.match
and.analysis
doesn't make much sense, since there isn't anything called from those repos.Can anyone think of a reason to keep this check in here? @RMI-PACTA/r-developers
Context: I'm planning to ensure checks against dev-versions of dependencies in
.match
(RMI-PACTA/r2dii.match#480).analysis
(RMI-PACTA/r2dii.analysis#501) and.plot
(RMI-PACTA/r2dii.plot#567) which captures the "upstream" direction, but do we need to capture "downstream" for some reason (if we're not executing any of that code)Relates to #386
The text was updated successfully, but these errors were encountered: