Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarifications on pkgdown workflows #1351

Closed
Tracked by #1350
maelle opened this issue Jul 26, 2022 · 2 comments
Closed
Tracked by #1350

Clarifications on pkgdown workflows #1351

maelle opened this issue Jul 26, 2022 · 2 comments

Comments

@maelle
Copy link
Member

maelle commented Jul 26, 2022

@krlmlr reg #1064 to follow https://pkgdown.r-lib.org/dev/articles/how-to-update-released-site.html I need some clarifications.

@maelle
Copy link
Member Author

maelle commented Jul 26, 2022

To make the workflow dispatch able to replace the released website do you agree we need to replace the lines

if: github.event_name != 'push'

with

if: github.event_name != 'pull_request'

@maelle maelle mentioned this issue Jul 26, 2022
5 tasks
@krlmlr
Copy link
Collaborator

krlmlr commented Jul 26, 2022

The pkgdown deployment workflow should be triggered for all branches named docs* ?

@cynkra cynkra locked and limited conversation to collaborators Aug 20, 2023
@krlmlr krlmlr converted this issue into discussion #1948 Aug 20, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Development

No branches or pull requests

2 participants