Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use GitHub Actions for Surge push #1467

Closed
wants to merge 37 commits into from
Closed

Conversation

wd15
Copy link
Collaborator

@wd15 wd15 commented Nov 28, 2022

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.

  • The comment back to the PR can be seen below.
  • I don't know how to update the Surge token (the current one is exposed), see Revoke token sintaxi/surge#491
  • The Nix Cache has been fixed and actually works now
  • The Surge teardown will be implemented in a separate PR.

Remember to tear down the live site when merging or closing this
pull request.

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.
Save pull request number as an artifact for other workflows.
@pfhub
Copy link
Collaborator

pfhub commented Nov 30, 2022

The new version of the PFHub website is available at https://random-cat-1467.surge.sh

@pfhub
Copy link
Collaborator

pfhub commented Nov 30, 2022

@, the new version of the PFHub website is available at https://random-cat-1467.surge.sh

@pfhub
Copy link
Collaborator

pfhub commented Nov 30, 2022

@, the new version of the PFHub website is available at https://random-cat-1467.surge.sh

@pfhub
Copy link
Collaborator

pfhub commented Nov 30, 2022

@, the new version of the PFHub website is available at https://random-cat-1467.surge.sh

@pfhub
Copy link
Collaborator

pfhub commented Nov 30, 2022

@wd15, the new version of the PFHub website is available at https://random-cat-1467.surge.sh

@pfhub
Copy link
Collaborator

pfhub commented Dec 1, 2022

@wd15, the new version of the PFHub website is available at https://random-cat-1467.surge.sh

@pfhub
Copy link
Collaborator

pfhub commented Dec 1, 2022

@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.
@pfhub
Copy link
Collaborator

pfhub commented Dec 2, 2022

@wd15, the new version of the PFHub website is available at https://random-cat-1467.surge.sh

@pfhub
Copy link
Collaborator

pfhub commented Dec 2, 2022

@wd15, the new version of the PFHub website is available at https://random-cat-1467.surge.sh

@wd15 wd15 closed this Dec 2, 2022
@wd15 wd15 deleted the issue1429-surge branch December 5, 2022 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use GitHub action for PR comment about Surge
2 participants