I would really like some love for shields/badges similar to https://shields.io/ . A few shields I had in mind: Build Status Build Error/Warning Count Build Lighthouse scores
Create a new cache (cold build) on the background
Sometimes, creating a cold cache can take a long time. Sites that take up to 90mins to create a cold cache are out there. Pressing that clear cache button is a very risky thing to do, if you run one of these sites. I myself have ran into the situation where I cleared the cache, my site wouldn't build anymore because of bugs/timeouts/X and your site would be stale for hours. Potentially running misinformation (about stock for example). So I'd like to propose being able to creating a new cache, while still being able to incremental build the current site. A way in which this could be achieved would be to have something even more awesome: being able to promote a build to production. This could be branch deploys, a different site, but I guess being able to run a cold build on the background would still fit this use case best.
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.
GitHub Deployments API
Add support for reporting deploys back to GitHub using the Deployments API ( https://docs.github.com/en/rest/deployments/deployments ). This would unlock the ability to protect PRs based on deployment rules, and to be able to use GitHub Actions based on deployment status.
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.
Azure Devops Integration
We've started to hear the request for integration with Azure DevOps on Gatsby Cloud over the past few weeks.
Support Context in Filesystem Routes API
We have context variables in our Gatsby-node builds and would love to have context support in Filesystem Routes API as that would make the code much cleaner
Support for Specifying NPM Version
Users should be able to set both the NPM and Node version for their sites on Gatsby Cloud
Add observability integration
I'd love a way to easily integrate our observability tooling (New Relic) to be able to see / query data for: * builds (how long is each build, average build times, where is the build spending the most time, etc) * logs of http traffic / requests to serve gatsby files to browser something like netlify's log drains would be dope. https://docs.netlify.com/monitor-sites/log-drains/