-
Notifications
You must be signed in to change notification settings - Fork 78
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
Astro Site: Please ensure the content does not contain any hard links, symlinks and total size is less than 10GB #345
Comments
Hello! Try using actions/upload-pages-artifact instead of actions/upload-artifact. This will take care of prepping your files in the right format for GitHub Pages. |
@yoannchaudet Thank you so much for your quick response. I guess it's because the upload I was using doesn't create a tar in a zip? I'll give it a try! |
Fixed my issue. The error message should be clearer. |
* build(deno): migrate to deno 2 build * fix(deno): resolve `astro dev` exceeds OS open files limit (os error 24) issue: denoland/deno#17757 * build(deps): bump astro * build(deno): action to deploy using deno * fix(deno): remove broken step (test) * fix(deno): update step * fix(deno): add version to action path * fix: add `uses` to deploy step * refactor: update extension, deno install scripts, add pages step * test: add text to validate deployment * fix: update upload artifact to upload the `dist/` dir not `dist` file * fix: LHTW * fix: use correct repo `actions/upload-artifact@v4` * fix: add id to upload artifact step * fix: name artifact `github-pages` * fix: try artifact v3 * fix: revert to artifact v4 * fix: use `actions/upload-pages-artifact@v3` actions/deploy-pages#345 * chore: remove test
Like many others I'm getting the dreaded error:
here's my yaml file:
The artifact file is produced and is under 1GB (about 1.6MB) it doesn't seem to contain any hard links or symlinks.
I've added a copy of it here, it's a very simple Astro site:
github-pages.zip
Out of desperation I tried to chmod all the files to 777 before publishing (as you can see in the pipeline.yaml). Unfortunately that didn't appear to work.
Any help you can offer would be sincerely appreciated as I've spent quite a bit of time trying researching, trying to find a fix, to no avail 😔.
The text was updated successfully, but these errors were encountered: