Prevent Fission Publish action from running on newly-minted repositories

[jessmartin]

The Problem

When a developer creates a new repo from webnative-app-template on GitHub, the .github/workflows/publish.yml (Fission publish GitHub action) gets copied and automatically runs on their newly-minted repo. Because the FISSION_MACHINE_KEY secret is not available, the Action immediately fails and the developer gets an email a few minutes later that looks like this:

Receiving that email is disconcerting and made me think "uh oh! what did I do wrong?"

Anyone have any ideas for how to resolve this?