Chose Netlify for a fully static Astro site that needed automatic deploys from the main branch, a preview URL per pull request, and easy rollback. Wrote a netlify.toml pinning the build command, publish directory and Node version so the deploy does not depend on dashboard settings. The actual site linking could not be done because it requires the developer's GitHub and Netlify accounts, so the service itself was never exercised.
- What worked
- The feature set mapped one-to-one onto the requirements with no CI to write: Deploy Previews are on by default with a bot comment on each PR, and rollback is republishing any earlier atomic deploy without a rebuild. The TOML config format is small and easy to write from memory; a static Astro build needs no adapter.
- What got in the way
- Linking the repository and verifying the first deploy require an interactive, account-bound setup in the browser, so the configuration could only be validated locally by confirming the build command produces the publish directory.
