cc

@keith - could you check the links & logo size/placement I used for MNF? I just took all the corresponding links that Google had and pointed to corresponding page here - https://lfprojects.org. Can check on my test domain here - https://cjthome.com

@KrauseFx - This main branch is gh-pages which I hope works with the automatic GitHub publishing, but if not we may need to change main branch to main / master and rename off of gh-pages.

Yes, I have to admit, I don't think it will auto-deploy, and I'm not sure where the page is hosted. I merged #96, but it never got deployed.

I believe Google may have changed the hosting (or maybe as you mentioned, it's just the branch?).

Yes, I have to admit, I don't think it will auto-deploy, and I'm not sure where the page is hosted. I merged #96, but it never got deployed.

Yeah tough to follow what happened here. I don't see any automatic deployment solutions to do the actual compilation on those older branches. I think at some point all the compiled files were just committed and served live from the gh-pages branch.

I believe Google may have changed the hosting (or maybe as you mentioned, it's just the branch?).

Very possible. If you want I can change all my references to master or main, then a merge of this and a rename of the default branch to match that should fix it. You'll just have to go Pages tab and hit "Github Actions"

Crawled some logs. It seems on the merge a few months ago - it deployed via GH Actions - https://github.com/fastlane/fastlane.tools/actions/runs/16841236940. I was confused briefly if this was even hosted on GH.

So confident this merge (as-is) with the change to swap GitHub Actions from "serve" to "GitHub Actions" will fix it up. GitHub might even swap it for you as the action deploys a Job.

Happy to hit merge, if okay with you @iBotPeaches ?

@KrauseFx - works for me. I'm around for 2h more hours to fix anything ASAP if it goes wrong.

Probably squash merge my ugly history :)

@KrauseFx - around for 3h if you want to give this a merge.