The gh-pages branch should be protected so that random people can't just splat our production deployment that people may be relying on for their voice.
The github action to deploy the production system should be able to push to the gh-pages branch though, for automated deployments.
Currently we do not have a configuration for the branch protection rule that allows both of these things to be true at the same time.