@maelle actually had an issue for this https://github.com/r-lib/devtools/issues/1754, which we decided to close in favor of package authors adding a release_questions object to their package rather than adding additional logic to devtools. But if we (tidyverse team) are going to start using this we can add it.
What happens now in write_codemeta
when called inside a package project
Rbuildignore codemeta.json
Adds pre-commit git hook
Message suggesting adding the release question (which is a bit superfluous given there's a git hook).
We're actually working on a codemetar
CRAN release for yesterday :joy: (release failed, we'll try again today).
Does it make sense to suggest this release question if you're going to add it to devtools
? If you add it and someone has the question inside their code they'll get asked the same question twice upon devtools::release
unless the phrasing is the same and devtools
only asks unique questions?
cc @cboettig
I think we'll use this in enough places it's worth baking in to devtools
Ok this question is now included in devtools::release()
if a codemeta.json file exists.
This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/
Most helpful comment
I think we'll use this in enough places it's worth baking in to devtools