Closed rjake closed 6 months ago
Please include a link to your workflow file, and to a failed build.
It's on our enterprise server so I don't have any links. Here is what we are running and the log for the setup-r-dependencies
step. Also, I just barely understand actions.
Do you have a DESCRIPTION
file at the root of the repository? Can you show that file?
Yes, I have added it in the comment above as well as the renv.lock
file
I don't know why this happens, but if you have an renv.lock
file, the correct action to use is setup-renv
, not setup-r-dependencies
.
Thanks for looking into it. We do have setup-renv
as a step before setup-r-dependencies
. I'm not sure where these two options need to go as we don't have pkgdown
in our DESCRIPTION
. I can contact our Posit rep if you think that is a better way to resolve this
- uses: r-lib/actions/setup-r-dependencies@v2
with:
extra-packages: any::pkgdown, local::. # <----
needs: website # <----
I think the proper renv way to handle this is to put pkgdown into renv.lock
and then use setup-renv
and not use setup-r-dependencies
at all.
I can contact our Posit rep if you think that is a better way to resolve this
That sounds like a good idea.
I am trying to adapt the
pkgdown.yml
workflow fromr-lib/actions
and it started failing on the stepsetup-r-dependencies@v2
. I think it related to this commit that was released with version 0.7.1 on 12/11/23. I posted on Stack Overflow but didn't get any responses. I'm not sure if there is something inpak
that can help, if ther-lib/actions
workflow example needs to be updated, or if there is a better place to get help. Any advice is appreciated.