pr-preview-action
pr-preview-action copied to clipboard
GitHub Action that deploys a pull request preview to GitHub Pages, similar to Vercel and Netlify, and cleans up after itself.
Our Github Pages configuration is set up to serve from a subdirectory and there is currently no documented way to address this with pr-preview-action. ## Example: **Preview Deployment Action** ```yaml...
https://github.com/www-learn-study/saraswati.learn.study/actions/runs/6727951896/job/18286524048 from https://github.com/www-learn-study/saraswati.learn.study/pull/42 has an example of a fatal git error what was not detected (return value ignored?) and check is reported as succesful although it failed: ``` (...) Checking...
This change simply adds a configurable `single-commit` option to be passed to `JamesIves/github-pages-deploy-action`
This workflow seems to target the "classic" GitHub Pages experience. However, nowadays there's also the newer workflow using https://github.com/marketplace/actions/deploy-github-pages-site ![image](https://user-images.githubusercontent.com/316517/194744490-5f05d71a-48b9-4baa-9e4c-5e5435b29177.png) I'm trying to combine the two actions but so far...
Instead of wasting time documenting the changes I'm making in #6 in either the current format or a new temporary one, I may as well take this opportunity to move...
It appears that [the default permissions on `GITHUB_TOKEN` have been changed to read-only](https://github.blog/changelog/2023-02-02-github-actions-updating-the-default-github_token-permissions-to-read-only/). By default, we cannot use this action until we change the settings of `Workflow permissions` to `Read...
I'm running into an issue where clicking on any link on the landing page on deploy preview take me to the page on actual deployment being served from the root...
This would enable pull requests to this repository to have a preview that is as per that request specifically.
This is just an initial proposal directly based on github-pages-deploy-action