Hi. I’ve had one of my gh-pages hosting a simple info/status page for a long time (several years), but a recent downstream configuration change required me to edit the URL of a media asset that was embedded in the HTML.
I’ve had an intermittent angry unicorn since committing that change (I’ve tried via both terminal/command line push and editing the HTML file in the github UI).
I say ‘intermittent’ because it does VERY occasionally work, but I would guess that for about 90% of the time I get the unicorn.
Has there been a change to how gh-pages work that means I have to do something new? I’ve searched the forum for other instances of this symptom but all I’ve found are reports that it got escalated, followed by “it seems fixed now”. I’ve been subject to the angry unicorn for over a week now.
This is using a custom subdomain, if that’s relevant (i.e.: mypage.mydomain.com). There’s nothing noteworthy in my page that I can imagine would break this functionality (although of course I would say that — if I could see it then I’d fix it )
This one has left me scratching my head for a bit. I think your site was so old, it ended in a very odd state. I spent a bit of time cleaning things up and you should be all good to go now. Sorry for the few manual rebuilds I had to trigger and for the annoyance.
Many thanks for this @yoannchaudet ! Yes, the site is very old and I haven’t had to touch it in a while — I’m embarrassed to confess that I’m no longer considered an engineer by vocation so git/github is something that I don’t get to use very much any more!
I did see the 503 error in the logs but the favico file hadn’t changed in 8 years so I dismissed it as just another symptom of the site only serving intermittently.
Thanks again for your help and to everybody else for jumping in to take a look!
Thank you @QuackingPlums and @yoannchaudet on posting question and answers here in the community. Looks like I’m not alone running into this issue.
My site with last update (> 10 years ago) was running fine. After I published a test post this week, Github unicorn has got angry. When I published same site to netlify (still with old css and JS), it worked fine.
I’m planning to update my site anyway, but it would be good to know how we can essentially ‘reset’ site.
This came up on the link above; you can ‘reset’ the site by disabling GitHub Pages and then re-enabling it. If you are using a gh-pages branch for this, you’ll have to rename the branch (git checkout -b website will do this fine) and then remove the gh-pages branch before you can actually disable the legacy pages.
I’ve verified this workaround on my Megaforge site.