Closed flxzt closed 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
that fixed it. thanks!
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.
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?
see:
https://github.com/flxzt/mercury/actions/runs/4523922956/jobs/7967401062
I am using the example shown in the readme: