The "Workers Sites" works differently than "Cloudflare Pages", at least from the developers side. You're using their wrangler tool instead of passing a git repo to their CI/CD setup.

you can definitely do something similar with workers sites.

we recently added workers kv - the storage mechanism behind workers sites - to our free workers tier, so you can host your static sites on workers for free as well.

pages is an evolution of that with better tooling/dx for people who want to get a static site up on our network and want things like deploy previews and pre-configured github integration.

if you want to just have workers do the hosting and want to do all the CI stuff yourself, you can use something like wrangler-action[1] to simplify the process on github actions, or just install wrangler[2] (our CLI) as part of your CI workflow and do `wrangler publish` at the end.

i wrote our github action, so if you decide to go that route, happy to help debug or look over the project to make sure it'll do what you want - i'm @signalnerve on twitter, DMs are open :)

[1] https://github.com/cloudflare/wrangler-action

[2] https://github.com/cloudflare/wrangler