Normalize build preview hostnames
Build previews use hostnames like this: https://build-12345678-9abc-def0-1234-56789abcdef0.gtsb.io/ https://siteprefix-branchname.gtsb.io/ These would be better: https://build-12345678-9abc-def0-1234-56789abcdef0.siteprefix.gtsb.io/ https://branchname.siteprefix.gtsb.io/ The use case here is whitelisting OAuth domains. I can't safely whitelist all Gatsby build domains. With the prefix as the third-level domain, I could safely whitelist *. siteprefix.gtsb.io for authentication operations.
Filter webhooks notifications by type
I'd like to be able to send notifications about production build issues to a different slack channel than PR builds
See Gatsby Cloud build trends
As a user that can access Gatsby Cloud, I want to be able to see the trend of my builds for each site so that I can determine whether a particular build was out of the ordinary (and for other reasons) The idea here is more of a sparkline / line chart, etc, in addition to the current build history view
Content sync preview with password protection
We need to use the content sync preview functionality but are unable because our previews must be password protected and content sync doesn't allow that. This seems like a feature that should be supported because preview is used for content you don't want anyone to find and even if you noindex the site it's still public and able to be found if you don't have a password set. Our current workaround is avoiding content sync entirely and manually building previews but there are issues with that approach. The preview status bar on the left doesn't give a good indication that a preview is building, there can be a delay between when the preview build hook is called and the page loads so you don't initially know it's building, and if you try to access a new page that's building you will get a 404. Preview builds also seem to take longer than normal to build so not having a better loading indicator is a big problem for us.
Support createRedirect force option on Gatsby Cloud
According to https://support.gatsbyjs.com/hc/en-us/articles/4406987771027-gatsby-plugin-gatsby-cloud , the force option for createRedirect is not supported. With the current behavior, if a page exists that matches the fromPath in the createRedirect options object, the page takes precedence over the redirect. Some hosting provider plugins allow setting the force option to override this behavior and allow the redirect to take precedence. It would be great to have this option for Gatsby Cloud (gatsby-plugin-gatsby-cloud).
Ability to turn off PR Preview builds
I would like the ability to turn off PR preview builds. I have numerous sites building off one repo, and pushes to a PR trigger ALL the builds where I would really only need 1 to trigger (the demo site). This is available on Netlify!
Cancel all builds in the queue, or automatic batching
Sometimes for various reasons a large number of builds could get into the build queue, causing long delays for new changes to get built. It'd be great to have an option to cancel all builds, so we can then manually trigger a new build that simply consolidates all changes. (I hack it by using some JS to automatically click all the "cancel build" button in the build queue, which actually works quite well. But I don't want to write that out every time, for apparent reasons :)) However there'd be different ways to achieve the same result, for example automatically grouping multiple webhook-triggered builds from the same source within a certain timeframe into one.
Gatsby Cloud with Microsoft Teams for Outgoing Notifications
We currently do not have the option to change the payload that Gatsby sends for outgoing webhooks, because of that, we are unable to make it work with Microsoft Teams. I have confirmed that with Gatsby Support, ticket #25213, and they suggested that i posted here as a feature request.