Kirill Müller
Kirill Müller
Nice! Should this be part of #331 (but mind the whitespace change)?
- Review links - Add "See also" or similar section to documentation - Rethink structure of change log messages later, for v1.0.0
We're using `callr::r_bg()` to run in non-interactive mode in the background. We can check the exit code of the process, available via (I think) `checks$get_exit_code()`. Maybe expose a function that...
It seems to me that the original issue was about getting errors if the submission to winbuilder failed. Retrieving the error logs is a neat idea too, let's try that...
Would this something that should be checked with each release (or e.g. each major release)? I remember seeing infrastructure for release questions (?) in the usethis/devtools space, can we integrate...
What else needs to be done?
We will create a NEWS file.
Perhaps we can wait with categorizing the entries until `pre_release()` ? In "changelog" format we would store raw entries, and put them under headers only when preparing a release? With...
Maybe `fledge::push_version()` ?