-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: failed to prune cache "assets" #5745
Comments
Pretty sure this is the same as #5673 |
I'm not sure but to give you more detail.. File Tree There are two nested Let me know if it still the same as #5673 |
@rahilwazir did you find the bug? |
Nah man, I changed my theme and it worked out for me. Are you using the theme? |
Yep, however I went and used |
Unfortunately we can't open issues on |
@neslinesli93, thanks for pinging. I will take a look at it. I've also enabled the issue tracker for the repo... |
Thanks man, I was sending you an email regarding the issue, but thankfully you enabled issues... |
I checked the issue and found the problem. The "bug" is the Hugo asked me to add the folder to the repo gohugoio/hugoThemes#577 (comment), because |
How can we do this by keeping your theme as a submodule? |
@digitalcraftsman, do you know maybe, if the issue regarding the hugo asset pipeline and the theme page (Netlify) is solved? |
@digitalcraftsman Sorry for tagging you again. Are there any news regarding Netlify? Is it possible to delete the |
The https://github.com/htr3n/hyde-hyde theme has the same problem. |
The Hermit theme has the same problem (as @kimfucious and I have reported here). |
For me force removing In my
Hope this helps |
Reasonable workaround. Thanks. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I'm using the following theme: https://github.com/rhazdon/hugo-theme-hello-friend-ng.git
And when I try to deploy it on Netlify, I face the following error.
This also happens on my local machine.
The text was updated successfully, but these errors were encountered: