Skip to content

Conversation

@Agilulfo
Copy link

Documentation improvement

Some of the steps on how to deploy were not clear and could benefit from a little more clarity

If you agree I would actually split the github actions section in two clearly separated scenarios:

  • build and deploy on the same repository
  • build and deploy on a separate repository

Sanity check:

  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?

env:
PAGES_BRANCH: master
BUILD_DIR: .
TOKEN: ${{ secrets.PUBLIC_TOKEN }}
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure from where this is coming from but to be consistent with the description above this should be secrets.TOKEN

Comment on lines -76 to -88
build:
runs-on: ubuntu-latest
if: github.ref != 'refs/heads/main'
steps:
- name: 'checkout'
uses: actions/checkout@v4
- name: 'build'
uses: shalzz/zola-deploy-action@master
env:
PAGES_BRANCH: gh-pages
BUILD_DIR: .
TOKEN: ${{ secrets.TOKEN }}
# BUILD_ONLY: true
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure why this job is in here.

To achieve what the instructions describe before this script the build_and_deploy job is sufficient

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.

1 participant