You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
GitHub pages (#19) only host the documentation the development version. Web browsing of the package on CRAN only shows the documentation of the latest release.
This make hard to browse or check the documentation of past release
Describe the solution you'd like
When publishing a GH release or at least when the tag of a released version is pushed, attach the documentation as a release assets.
Additional context
The documentation generation and attachment to the release should be automated to avoid human errors.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
GitHub pages (#19) only host the documentation the development version. Web browsing of the package on CRAN only shows the documentation of the latest release.
This make hard to browse or check the documentation of past release
Describe the solution you'd like
When publishing a GH release or at least when the tag of a released version is pushed, attach the documentation as a release assets.
Additional context
The documentation generation and attachment to the release should be automated to avoid human errors.
The text was updated successfully, but these errors were encountered: