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
npm-publish has a nice feature called --dry-run that lets you test what the command is going to do without actually doing it. It might be nice to have something like that in actions-gh-pages.
That way, on each pull request, I can see if this actions-gh-pages step in the CI workflow throws any errors, and I can get a list of what would've been published to the gh-pages branch (and any other helpful info). This would give me confidence that it will work fine when pushing/merging into master.
The text was updated successfully, but these errors were encountered:
what is the status of this Issue? I can see a PR already. Is it working? Why is it not yet merged? If there are still some TODO's for the PR I might be able to support (if OK of course).
npm-publish has a nice feature called
--dry-run
that lets you test what the command is going to do without actually doing it. It might be nice to have something like that inactions-gh-pages
.It could look like this:
That way, on each pull request, I can see if this
actions-gh-pages
step in the CI workflow throws any errors, and I can get a list of what would've been published to thegh-pages
branch (and any other helpful info). This would give me confidence that it will work fine when pushing/merging into master.The text was updated successfully, but these errors were encountered: