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
Right now if the autodetection fails you can set crayon options to turn on color for the rcmdcheck output, e.g. options(crayon.enabled = TRUE).
For the GitHub Actions use case it would be useful to have a rcmdcheck specific option or environment variable to control this, then the setup-r action can enable this without affecting color elsewhere in the workflow, e.g. hadley/mastering-shiny#132
The text was updated successfully, but these errors were encountered:
This would still be somewhat useful to have a rcmdcheck specific option to control the color, but for now we are setting the crayon option before running rcmdcheck(), which works ok.
Right now if the autodetection fails you can set crayon options to turn on color for the rcmdcheck output, e.g.
options(crayon.enabled = TRUE)
.For the GitHub Actions use case it would be useful to have a rcmdcheck specific option or environment variable to control this, then the setup-r action can enable this without affecting color elsewhere in the workflow, e.g. hadley/mastering-shiny#132
The text was updated successfully, but these errors were encountered: