In this post I am going to explain how to set up a basic workflow that uses an existing GitHub action. This workflow will deploy a static web site ...
For further actions, you may consider blocking this person and/or reporting abuse
Nice write up!
I think
${{ secrets.ACCESS_TOKEN }}in your example can be replaced with${{ secrets.GITHUB_TOKEN }}, which is a repo-scoped token automatically generated for you by GitHub. Did you try this?Thanks!
I just tried it, but it didn't work.
Also, I couldn't find the documentation about this auto generated token.
Hmmm. It’s documented here:
But maybe it doesn’t carry the right permissions for your use case. Did you get a permissions error?
When the Action try to push the changes, it pops this error in the logs:
fatal: could not read Password for 'https://***@github.com': No such device or addressThat must be a permissions error. The personal access token that I generated before (
ACCESS_TOKEN) had full control of my private repositories.could you upgrade this article to v3
Done !
Fixed it ! 👍
How do we implement the process.env with plain html/css/vanilla js?
Please explain -- why should I use it? GitHub Pages are already automatically deployed. What am I missing?
For project like React, Vue or Angular you will need to build the project to have the html,css and js files that Github Pages can serve.
Github Actions will automate this step for you.
You mean, for sites that are not simple Jekyll? Got it.
Thanks 😀