Kirill Müller
Kirill Müller
Are you suggesting to run pkgcheck locally as part of `pre_release()` ?
What would the integration look like?
You can enable workflows on `cran-*` branches only, fledge won't need to do anything here. It seems worth documenting this pattern.
NEWS -> tags is difficult anyway, we need to rethink this. At a first step this could be a list of tags that are missing, in a next step perhaps...
This and many many other issues will be much easier with #331.
Can we deploy automatically, but only if the documentation changes? We're still running a huge build matrix...
We'd assume that `gh-pages` contains the last deployed website, and deploy to Netlify only if the current state has changes? Of course this requires stable pkgdown builds, which isn't always...
And also render `README.Rmd`.
Needs {tasq}.
`document()` is now done in our workflows, rendering README remains manual because it's unstable all too often. I wonder if the GHA workflow could render README *twice*, and commit only...