Use GitHub Actions for Surge push #1467
Conversation
Add an updated build for Surge and Jekyll. This will be the basis for the new shell.nix eventually.
New Surge implementation on GitHub Actions. Removing Surge push from Travis CI and using GitHub Actions instead with an updated Nix build.
Surge workflow launches and does nothing. It is just used to prompt a workflow on master that has access to the secrets.
Use a more sensible name for the workflow that signals to other workflows that there is a new pull request.
Event name was incorrect.
Save pull request number as an artifact for other workflows.
|
The new version of the PFHub website is available at https://random-cat-1467.surge.sh |
|
@, the new version of the PFHub website is available at https://random-cat-1467.surge.sh |
|
@, the new version of the PFHub website is available at https://random-cat-1467.surge.sh |
|
@, the new version of the PFHub website is available at https://random-cat-1467.surge.sh |
|
@wd15, the new version of the PFHub website is available at https://random-cat-1467.surge.sh |
|
@wd15, the new version of the PFHub website is available at https://random-cat-1467.surge.sh |
|
@wd15, the new version of the PFHub website is available at https://random-cat-1467.surge.sh |
Surge push is now executed by GitHub actions.
|
@wd15, the new version of the PFHub website is available at https://random-cat-1467.surge.sh |
|
@wd15, the new version of the PFHub website is available at https://random-cat-1467.surge.sh |
Switch the Surge push to use GitHub Actions.
Fixes #1429
The push occurs with an event that does not use a pull_request trigger, but a workflow_run trigger. This needed to be tested from master, not a pull request, see the new surge.yml file on master. The pullrequest.yml file on this branch triggers the surge.yml workflow.
Remember to tear down the live site when merging or closing this
pull request.