Kind of; flyctl deploy will “magically” build and deploy your app. They show how incredibly easy it is to throw this into GitHub Actions, which I’ve probably done about 8 times in the past week, and it seems to work about as well as you’d expect. (My only deviation from the example is that I limit the branches to deploy to just master.)

To me, flyctl deploy is perhaps even better, because it is VCS agnostic and integrates with existing pipelines. I think it is fully worth it.

I agree that it's perhaps even better. With Fly, I feel safe that whatever I want to do now or in the future, I can build on top of the building blocks for it—no matter if there's an "integration". For example, when Vercel added GitHub integration, you couldn't trigger it based on specific logic (tags, branch pattern match) and a bunch of limitation that they use them for up-selling (using GitHub Enterprise/Org requires a Pro account).