This repository has been archived by the owner on Apr 10, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
build is failing #16
Comments
@7yl4r Is this the same issue that I am having? |
I suspect so. I have just been doing manual builds since we are expecting to move over to the new site soon. |
Okay gotcha. Okay if I ask you to do another build later today?
… On Jul 20, 2022, at 11:51 AM, Tylar ***@***.***> wrote:
I suspect so. I have just been doing manual builds since we are expecting to move over to the new site soon.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Yes. Just let me know when and I'll push the button on my computer. |
Okay, I think it's ready to go. I can't guarantee that I won't have additional tweaks but I'm trying to keep them to a minimum. Can you do a build when you have a chance? |
OK. Done. I checked the site and I think it looks good. |
Thanks Tylar. I had to make a couple of small tweaks (I named one of the files 2002 instead of 2022, eek) - could you re-run when you have a moment? |
done! |
Thanks!
… On Jul 20, 2022, at 6:46 PM, Tylar ***@***.***> wrote:
done!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Ugh sorry - can I ask you to rebuild one more time? No rush.
On Wed, Jul 20, 2022 at 7:27 PM Torie Ketcham - NOAA Affiliate <
***@***.***> wrote:
… Thanks!
On Jul 20, 2022, at 6:46 PM, Tylar ***@***.***> wrote:
done!
—
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKTSOFWAGVX3SCDSYMPCIBTVVB6STANCNFSM5YUYBK6A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Just built & pushed. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Builds here seem to be having this issue but the workarounds suggested there do not seem to be working. I looked into the source code of the jekyll-build action and was not able to determine where that
docker run
command is being generated.The text was updated successfully, but these errors were encountered: