Don't post preview comment until actual GitHub Pages deployment workflow completed?

[vincerubinetti]

Testing this out, and it works great! One thing I noticed is that, understandably, the action only waits for itself to finish to post the comment on the pull request. It would be great if that could somehow be delayed until the actual GitHub Pages deployment process has completed so that the preview link works as soon as it's posted. Right now, there's a short period of time between when the comment is posted and when the link will actually go somewhere.

I'm using this action in a website template that will be used by many non-technical users, and I could see them getting confused by there being a link but the preview not being ready yet.

As for how to implement this, I'm not sure. Is it possible for this Action to somehow add the associated GitHub Pages deployment run as a Status Check to the PR? Maybe it's possible to use action-wait-for-check or some similar action to wait for the deployment to succeed in the middle of running this action (I guess after committing to the gh-pages branch so the build starts, but before returning successfully).

Or maybe a stop gap could simply be adding a message to the pull request comment that clarifies that the preview WILL be available (after a short moment) at the following link.

PR Preview Action v1.2.0 :---: Built preview to branch gh-pages at 2022-11-21 20:33 UTC :rocket: Your preview will be available at https://vincerubinetti.github.io/test/pr-preview/pr-1/ once GitHub finishes deploying it

[rossjrw]

Good idea! Off the top of my head, I don't think this action can get any information about the Pages build process itself. This is definitely worth spending some time looking into - thanks for the contribution!

[vincerubinetti]

Yeah, there doesn't seem to be a way to programmatically get info about the process at all. Maybe one of these endpoints can accept the Actions token as authentication? https://docs.github.com/en/rest/pages#get-latest-pages-build

Since users of this action can't customize the text in the pr comment, I'd strongly request tweaking the wording carefully so people inexperienced with GitHub won't get confused.

[ElioDiNino]

Since users of this action can't customize the text in the pr comment, I'd strongly request tweaking the wording carefully so people inexperienced with GitHub won't get confused.

I strongly agree here and I really like the addition you added that says "once GitHub finishes deploying it". I think this would reduce a lot of confusion