Lorenz Walthert

Hi @tlorusso. I was using this package at work and now I quit, so for me there is no incentive to work on that anymore and I already have too...

I saw that in `CONTRIBUTING.md`... So this would just give an error message and say "run pre-commit clean" or are there interventions with a smaller scope?

Problem is that the virtual environment is hard to access for the end user, so if pre-commit just ran a `renv::restore()`, the problem would be solved I think.

Also, how to determine the environment is broken? Can we record the R version when the environment is installed and then check it's the same in `healthy` or how would...

thanks, I think we can use {renv} APIs to persist the R version in use as a _setting_ in `renv/settings.json`, so hence we should be able to detect mismatching R...

Sorry I don’t maintain this actively anymore.

I am experiencing a similar issue. I can think of the following reason: To upload the data from the container to S3, I guess AWS uses the S3 API in...

You could even do the R code inline in `.pre-commit-config.yaml`, then you don't need `bin/renv.R`. ``` entry: Rscript -e '...' ```

Well just use `stop()`?

Sorry @owenjonesuob for the delay. Here's my review: > If it catches a warning, it fails and explains that it's due to a roxygen error. Can you tell me when...