github-pages-deploy-action VS tokens

The interesting part is towards the bottom where we build the frontend code and make use of the github-pages-deploy-action step to automatically make a new commit with the compiled frontend code to a gh-pages branch.

Finally, will do the deploy on github pages using the scripts from JamesIves/github-pages-deploy-action, and create a branch gh-pages with the code from apps/web/build.

- Deploy to GitHub Pages using GitHub Actions

For Storybook deploy, we will use github-pages-deploy-action

If you've built a site that can be rendered statically, then you can probably set up a GitHub Pages deploy via GitHub Actions (since Pages supports only Jekyll by default, you need this for any other static site generator). But if you have a server component, then you'll need to host it some other way.

Around three years ago I created the github-pages-deploy-action project as my first real venture into the world of open source. I built this action so I could make continued updates to a blog while being away from my work laptop. The community response has been fantastic and I'm very happy with how it has evolved over the years as a result. I even had the opportunity to be interviewed by GitHub for my involvement back in 2020 which you can read here.

This action is a composite action using shell scripts for installing necessary tools and preparing docs and makes use of JamesIves/github-pages-deploy-action for deploying the docs to a GitHub Pages branch.

github-pages-deploy-action is used to push a static exported site to gh-pages branch.

Lastly, we use another Action to deploy our project to GitHub Pages – but only if the workflow is running on the master or main branch (we don't want development branches to be deployed to the public!). We point this action to the build/distributions folder, which is where building a Kotlin/JS project creates the final .js and .html artifacts.

Click on your profile in the top right corner > Settings > Developer settings, or visit: https://github.com/settings/tokens.

First of all, you need to generate a new GitHub Token. You can generate a token in your GitHub account settings at https://github.com/settings/tokens. Make sure to add the ‘read:packages’ scope to your token.

First, generate the GitHub token here.

Environment Variables Create a file .env in the root folder and add your own github api token as below

Go to the Personal access tokens area in the Developer settings of your GitHub profile and click Generate new token.

Versioning The initial step in this workflow involves generating version numbers based on git tag numbers. To access repository information, it's necessary to include a GitHub token in the secrets. You can create a GitHub token by following this link. Please keep in mind that secret names cannot start with the term GITHUB. For instance, you might save your GitHub token as TOKEN_GITHUB.

GitHub has tucked the personal access tokens admin in a slightly hard-to-find location. From anywhere in GitHub, you can click on your profile image → Settings → Developer Settings → Personal Access Tokens.

Generate a classic PAT (personal access token) from Github with repo and admin:org scopes at least.

YOUR_TOKEN="no_token_for_you" # IMPORTANT: your Github API access key, make one at "https://github.com/settings/tokens"

You should click on that and then you will see Tokens (classic) which will bring you to https://github.com/settings/tokens