#9 helps to share a contributor's Github Pages link for reveiwer to preview the webpage change.
However, this approach is not well-suited for collaboration because:
- Contributors cannot obtain unique deployment links for different PRs.
- It requires contributors to create a dedicated preview branch (e.g.,
do-something-preview) with an additional commit to change baseurl to /asterinas.github.io, while the actual PR is submitted from the original feature branch (e.g., do-something).
I find vercel is great as a better solution to preview PR changes for the website.
- github and vercel gather hisotry preview changes:
Screenshots
example: https://github.com/os-checker/unsafety-propagation-graph/deployments
- the Vercel bot automatically builds and sends notifications for multiple preview deployment links on each pushed commit in single PR: contributors do not need to take any extra steps; they simply wait for the preview link to be generated for reviewers.
example: os-checker/unsafety-propagation-graph#63

#9 helps to share a contributor's Github Pages link for reveiwer to preview the webpage change.
However, this approach is not well-suited for collaboration because:
do-something-preview) with an additional commit to changebaseurlto/asterinas.github.io, while the actual PR is submitted from the original feature branch (e.g.,do-something).I find vercel is great as a better solution to preview PR changes for the website.
Screenshots
example: https://github.com/os-checker/unsafety-propagation-graph/deployments
example: os-checker/unsafety-propagation-graph#63
