Daniel Possenriede

I'd recommend the `helper-*` approach, because AFAICT that is the only one that automatically loads the vcr setup when developing/testing interactively (which I'd want as a developer) and does not...

> Testthat docs [no longer recommend](https://testthat.r-lib.org/reference/test_dir.html#special-files-1) using `helper-*.R` files: Just found this https://github.com/r-lib/testthat/pull/1626 1. gotta love Jenny's commit messages/PR titles 2. Seems like Hadley agrees with us now.

`use_vcr()` creates a `setup-pkgname.R` (as [documented here](https://github.com/ropensci/vcr/blob/4579c52b5113009b2272b9316c63adfbf02261c0/man/rmdhunks/cassette-names.Rmd#L21), where `pkgname` is the name of the package using vcr) whereas some of the documentation refers to `setup-vcr.R`, (EDIT) e.g. here https://github.com/ropensci/vcr/blob/4579c52b5113009b2272b9316c63adfbf02261c0/man/rmdhunks/setup.Rmd#L20 I...

Yes, that is correct. You can put all setup code into one `helper*.R` file or into separate files. At present, `use_vcr()` would create a `helper-tidytags.R` (if not present already) and...

> Arguments on subsequent lines of a multi line function call must be named. IMHO this should not be or only be implemented as a (non-default) `strict` option, since this...

Yes, both styles should be allowed.

The related postgres extension install issue is tracked over at https://github.com/duckdb/duckdb-r/issues/23, [spatial is working](https://github.com/duckdb/duckdb-r/issues/23#issuecomment-1985276933).

Me neither, unfortunately. This post describes [how it works generally](https://mkaz.blog/code/code-signing-a-windows-application/) with signtool.exe on Windows. Apparently there is also as `signcode` in mono - so could be possible on e.g. Ubuntu...

Maybe the gh (GitHub cli) workflow helps: https://github.com/cli/cli/blob/trunk/.github/workflows/releases.yml It uses [goreleaser](https://github.com/cli/cli/blob/8f28d1f9d5b112b222f96eb793682ff0b5a7927d/.github/workflows/releases.yml#L41) and https://github.com/mtrojnar/osslsigncode ([here](https://github.com/cli/cli/blob/8f28d1f9d5b112b222f96eb793682ff0b5a7927d/.github/workflows/releases.yml#L32)) for signing the exe files. MSI files are built separately (https://github.com/cli/cli/blob/8f28d1f9d5b112b222f96eb793682ff0b5a7927d/.github/workflows/releases.yml#L133). A suitable cert should be...

Here is a post that describes the process in detail: [Automatic Code-signing on Windows using GitHub Actions](https://federicoterzi.com/blog/automatic-codesigning-on-windows-using-github-actions)