The instructions for new repos should probably mention that there are two options available under Settings > Pages: "Deploy from a branch" and "GitHub Actions", and specify that deploying from a branch (and which branch) is the one to use.
The "GitHub Actions" option is opaque and what GitHub actually has it do is out of the repo owner's control — and out of this template's control. It's also still designated a Beta, and not 100% stable.
I noticed several font project repos using this setting with the result that the README buttons linking to the Fontbakery HTML reports on the .io site broke, silently, for several weeks. There's not a lot of insight available into the "GitHub Actions" option when it changes, but there doesn't appear to be a benefit to using it ... plus, if everyone uses the same setting, then there's no chance of divergence.
The instructions for new repos should probably mention that there are two options available under Settings > Pages: "Deploy from a branch" and "GitHub Actions", and specify that deploying from a branch (and which branch) is the one to use.
The "GitHub Actions" option is opaque and what GitHub actually has it do is out of the repo owner's control — and out of this template's control. It's also still designated a Beta, and not 100% stable.
I noticed several font project repos using this setting with the result that the README buttons linking to the Fontbakery HTML reports on the .io site broke, silently, for several weeks. There's not a lot of insight available into the "GitHub Actions" option when it changes, but there doesn't appear to be a benefit to using it ... plus, if everyone uses the same setting, then there's no chance of divergence.