I want to use Renovate to maintain my site dependencies. Currently when Renovate creates a PR, Gatsby Cloud builds are not triggered. This prevents us from checking build previews and/or enabling automerge. I would like control of this.

There is a chance that the *. gatsbyjs.io domain gets crawled and indexed by search engines, which may be unwanted behaviour, especially if a custom domain is configured.

For a site on Gatsby Hosting, I would like to be able to add simple password protection for users to be able to access the site.

In order to introduce NX to our Gatsby Application, we were unable to leverage gatsby-*.ts files for plugins and themes that are not structured as local plugins of our primary Gatsby Application. Instead of having to transpile our themes' gatby-node.ts files to JS, we would deeply appreciate native support! Thanks. https://www.gatsbyjs.com/docs/how-to/custom-configuration/typescript/#other

It would be nice to be able to customize the payload and request method (i.e. GET/POST) of the outgoing we hook notification. I'm trying to set up Algolia DocSearch crawler on GitHub Actions after a successful build on Gatsby Cloud.

Having the web UI as the sole interface for configuring a large number of sites is just painful. Headless Gatsby Cloud, no ?

Well done

redSiegeTestPost

Use a custom domain for Deploy and CMS Preview builds