shalzz / zola-deploy-action

Github action for building a Zola site and deploying to Github Pages
MIT License
234 stars 91 forks source link

deployment fails with "error: wrong number of arguments, should be 2" #71

Closed flxzt closed 1 year ago

flxzt commented 1 year ago

see:

https://github.com/flxzt/mercury/actions/runs/4523922956/jobs/7967401062

I am using the example shown in the readme:

name: Zola on GitHub Pages

on: 
 push:
  branches:
   - main

jobs:
  build:
    name: Publish site
    runs-on: ubuntu-latest
    steps:
    - name: Checkout main
      uses: actions/checkout@v3.0.0
    - name: Build and deploy
      uses: shalzz/zola-deploy-action@v0.17.2
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
shalzz commented 1 year ago

The latest commit branch should resolve this. Try using uses: shalzz/zola-deploy-action@master in your workflow file.

Also if you're building a site without a theme submodule, disable pulling in the submodule with the BUILD_THEMES flag mentioned here: https://github.com/shalzz/zola-deploy-action#environment-variables

flxzt commented 1 year ago

that fixed it. thanks!

muzimuzhi commented 1 year ago

The actions/checkout action learnt a new input set-safe-directory: <path> since v3 (see https://github.com/actions/checkout/commit/0ffe6f9c5599e73776da5b7f113e994bc0a76ede), so I think sth like

      - uses: actions/checkout@v3
        with:
          set-safe-directory: '*'

should work as well.

florianhumblot commented 1 year ago

The latest commit branch should resolve this. Try using uses: shalzz/zola-deploy-action@master in your workflow file.

Also if you're building a site without a theme submodule, disable pulling in the submodule with the BUILD_THEMES flag mentioned here: https://github.com/shalzz/zola-deploy-action#environment-variables

any way to make this a new release so that we can pin our action workflows to that instead of a potentially changing master?