I think it's worth making a release v0.17.3 with the latest fix for the dreaded error described in #72.
The latest version on master seems to address all issues, and this is summarized below.
The '*' signs pointing to the sass and themes directories are not playing well with the Set safe directories portion of the pipeline
72 attempted to fix this, and it was tested by multiple people (and worked)
This comment confirms that the fix worked on repos with git submodules
Multiple others (including myself) have confirmed that the latest version on master works for relatively complex sites that depend on sass, but not git submodules.
All in all, I think the fix on master should be released as a version so that folks can make the choice if they want to continue using v0.17.2 (which didn't work for a lot of us), or v0.17.3, which works for others. Pinning the version number makes a lot more sense than using shalzz/zola-deploy-action@master in the longer term.
I think it's worth making a release
v0.17.3
with the latest fix for the dreaded error described in #72. The latest version onmaster
seems to address all issues, and this is summarized below.'*'
signs pointing to thesass
andthemes
directories are not playing well with theSet safe directories
portion of the pipeline72 attempted to fix this, and it was tested by multiple people (and worked)
master
works for relatively complex sites that depend on sass, but not git submodules.All in all, I think the fix on
master
should be released as a version so that folks can make the choice if they want to continue usingv0.17.2
(which didn't work for a lot of us), orv0.17.3
, which works for others. Pinning the version number makes a lot more sense than usingshalzz/zola-deploy-action@master
in the longer term.Thanks for all the work on this btw!