Whenever a preview environment for a PR is created, Gatsby Cloud generates a preview url. It will be nice to receive this url value as build variable, like GATSBY_PREVIEW_URL This helps in many situations. For example: Our team focuses on UI testing but we feel if we have the preview URL as a build variable we can speed up the process of generating sitemaps and test the deploy links for each and every PR.

Especially for e-commerce, it would be nice to show a tweaked version of a site during a timeframe. Prepping that work in a separate branch (visual theme changes, pulling data from a different dataset, etc) and then on a given time swap master to point to that branch and then have it switch back at another time would be amazing. I don't care if it's in the GC UI or done through the (planned?) management API.

We use Sanity and webhooks to trigger builds whenever a document is published in Sanity. We also have a large number of editors, as well as scheduled processes syncing data from other places. This leads to a lot of builds/invocations that are unnecessary. It would be great if we could debounce builds (at least triggered by webhooks) to once every {n} minutes.

Currently lighthouse reports are generated only for the home (/) page. It would be useful to have this configurable. Example use case: all of our regional gatsby sites have the'/' redirected to /xx/ page (replace xx with regional ID). Due to this, lighthouse reports are not generated in gatsby cloud.

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.

My team and I have a process of verifying our work in preview builds. If we add redirects those also get verified. We need the redirects working in the preview builds.

I noticed that onPostBuild in gatsby-node is not called during a preview build. I understand why this would not be called as a means to save time, however I have some post processing that I need to do to make the preview complete. Since the content sync can correlate the content in my CMS with the page to open in preview, I figured it could add that url in the webhook payload, to allow me to process that data separately. For example, it could add something like: changedUrl: "https://my-site.gtsb.io/blog/post/test/" Here is an example payload of a webhook as it currently is: { body: '# [Gatsby Cloud](https://www.gatsbyjs.com) Build Report\n' + '**my-site**\n' + '\n' + ':tada: Your build was successful! [See the Deploy preview here.](https://my-site.gtsb.io)\n' + '\n' + '## Build Details\n' + '\n' + '[View the build logs here.](https://gatsbyjs.com/...)\n' + '\n' + ':clock1: Build time: **4m**\n', buildId: 'abcd', workspaceName: 'my-site', siteName: 'my-site', deployPreviewUrl: 'https://my-site.gtsb.io', logsUrl: 'https://gatsbyjs.com/dashboard/...', duration: '215', resourceId: 'abcd', resourceType: 'SITE', event: 'PREVIEW_SUCCEEDED' }

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

Currently invocation logs can be viewed for individual Gatsby Function endpoints for a particular build under the Functions tab on the build page. We find it useful to view the logs for these endpoints, but sometimes it can be difficult to determine which build we need to check the logs for when trying to trace a particular issue. We use Shopify as a data source, so this triggers a Cloud Build whenever something changes in our store. This can result in new builds occurring several times a minute. It would be great to have a way to view all the invocation logs for a particular Gatsby Functions endpoint all on one page (regardless of the build).

Add an option to handle 404s on server side. Benefits: 1/ if a build for new content is not finished yet, be able to return the page from the server side 2/ resolve similar content on server side and handle permanent redirects