I'm thinking atm, and will try to add `main` and `template` to the auto-build targets.
I'm thinking atm, and will try to add
main and template to the auto-build targets.maintemplatemain ones it's renamedlive gets published to GHCR. So that may be the most desirable?branches: was the old-school "protect against push to GHCR" idea before I changed it to only push live.branches: filtering for the auto-build triggers would solve that. So that way every branch gets built no matter its name. We're exactly as safe as before, since the deploy/sign steps only run for live.template (main atm) and live to build? If we want all other branches to be non-building, I could just list the exact branches.workflow_dispatch: trigger).live, main and template. As planned.branches: filter. This is what I just realized that we may need to do. Since it turned out that PRs run in the SOURCE repo/branch, not the target. So PRs from let's say branch: fix-foo -> merge into startingpoint:main would fail to run its GHA if we don't remove that filter. If PRs are working the way it seems.main contains the old workflow file.fix-something and submit it to you.main branch workflow won;'t build fix-something and therefore nothing happens. 0 actions are listed.main (old) to match the proposed feature branch, so that the action runs.main branches workflows?live as the main branch for it to be the one displayed when opening the repo

livelivelivelivelivelivebranches:branches:branches:workflow_dispatch:branch: fix-foo -> merge into startingpoint:mainfix-somethingfix-something