devtools

devtools copied to clipboard

check_win_devel interface is "too cute"

2

I'm trying `check_win_devel()` on a package for which I'm not the primary maintainer. Thus, the default behavior (e-mailing the primary maintainer as pulled from the DESCRIPTION) is not what I...

MichaelChirico

```R path

hadley

`document(quiet = TRUE)` is too quiet when a required package is not installed

1

When running `document()` with the argument `quiet = TRUE` on a package where another required package is not installed you get the following “question”: ``` Selection: ``` With no information...

haugedal

Once https://github.com/r-lib/covr/issues/543 is done. Remember to test interactively using https://github.com/hadley/testcoverage.

hadley

Discourage use of `build_vignettes()`

3

Since it creates artefacts in a way that we no longer recommend.

hadley

fix #2449 If the pkgdown config is not okay, then it errors, should it just warn? If we decide to keep on going, we could use ```r tryCatch( pkgdown::check_pkgdown(), error...

olivroy

:smile_cat:

maelle

Adds a missing "for" in the sentence about checking results in 5-10 min.

jgabry

Change `quiet` default for `build_site()`

2

I load devtools automatically in my R profile and always check my site rendering with `build_site()`. By default this wrapper suppresses output (`quiet = TRUE`). Unfortunately this means you can...

TimTaylor

devtools::test() report failures not reported with rcmdcheck(), the “Run Test” button in RSudio or e.g. testthat::test_dir(). Also, my package under test seems to work well. I am testing a package...

Pisca46