search

BryanSchuetz / jekyll-deploy-gh-pages

A GitHub Action for building a Jekyll site (with custom plugins) and deploying it back to your gh-pages branch.
118 stars 60 forks source link

Not deploying the latest commit #16

Closed thinkyhead closed 6 months ago

thinkyhead commented 4 years ago

I now have the action working, but when it deploys the site it is not building the most up to date version of the site (i.e., master:HEAD). Instead it checks out the branch from some earlier point in time.

I have not yet determined what commit it is deploying, exactly. I tried adding an extra commit and triggering the workflow to see if it was simply building from the previous commit, but this was not the case.

How is it possible that an older version of the 'master' branch is being checked out and published? Is there something that GitHub may be caching that is throwing us off?

For testing I changed the workflow to trigger on a branch named 'deploy' instead, but this didn't seem to help. I'm doing some testing now to see if 'deploy' gets published or if 'master' gets published when the action is triggered by a push to the 'deploy' branch.

If this test is inconclusive I will follow up soon by copying and hosting the action within the repo instead, and then I can add logging to see what's amiss.

Darn. On the first test I got this spurious error complaining about zeitwerk needing a newer Ruby. That shows up once in a while, but I don't know why. Possibly these runners are not all alike. Let's see if I just do another push…

I will follow up with more information as it progresses.

thinkyhead commented 4 years ago

Ok, so that deploy action did go through without an error. I'm doing a couple more with small changes to see if they get published properly or not…. If these tests pass then I'm going to conclude that sometimes this spurious Ruby error is causing it to fail, and I was mistaking this for a bad deployment.

thinkyhead commented 4 years ago

Who knows why, but this error cropped up once again! https://github.com/MarlinFirmware/MarlinDocumentation/actions

image

thinkyhead commented 4 years ago

The next deploy action did not throw an error. But it also didn't publish the HEAD. So, attempting another deploy…

NOPE! Action succeeds but the site doesn't change.

thinkyhead commented 4 years ago

Two tries, and same result. The site deploys, and the gh-pages branch is even updated, but the contents of gh-pages are stale. Very strange.