Support secrets.GITHUB_TOKEN

[multimeric]

If you are deploying to a gh-pages branch of the current repo, you should be able to use secrets.GITHUB_TOKEN instead of needing a deploy key at all. This would then work the same as all the other github-pages deployment actions, e.g. https://github.com/peaceiris/actions-gh-pages#github-actions-for-github-pages.

This would massively reduce the setup time for using this, since GITHUB_TOKEN exists by default, whereas creating an access token is a bit of a pain.

[oscarmorrison]

Yes. Something like github-token: ${{ secrets.GITHUB_TOKEN }} would be excellent

[maiwald]

I have switched to peaceiris/actions-gh-pages. It is not as specialized as gatsby-gh-pages-action but supports GITHUB_TOKEN. Their README has instructions for deploying Gatsby sites.

[sergiomcalzada]

You can do it just with

name: Gatsby Publish

on:
  push:
    branches:
      - gatsby

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v1
      - uses: enriikke/gatsby-gh-pages-action@v2
        with:
          access-token: x-access-token:${{ secrets.GITHUB_TOKEN }}
          deploy-branch: main

[log-line]

You can do it just with

name: Gatsby Publish

on:
  push:
    branches:
      - gatsby

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v1
      - uses: enriikke/gatsby-gh-pages-action@v2
        with:
          access-token: x-access-token:${{ secrets.GITHUB_TOKEN }}
          deploy-branch: main

Just leaving a quick comment on why/how this works: https://docs.github.com/es/developers/apps/building-github-apps/authenticating-with-github-apps#http-based-git-access-by-an-installation

Nice trick @sergiomcalzada