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).

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.

We've started to hear the request for integration with Azure DevOps on Gatsby Cloud over the past few weeks.

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

As a marketer, I want to be able to share a page that would be redirected based on language and still keep the query parameters for analytics purposes. Use case: I have a post with the following url example.com/p/new-product The language based redirects to example.com/produit/nouveau-produit if the language and to example.com/product/new-product for the rest I want to be able to keep the query parameters in the URL after the redirection. So example.com/p/new-product?utm_source=instagram redirects to example.com/produit/nouveau-produit?utm_source=instagram (and keeps the utm_source so we don't lose the analytics tagging in the redirect) This is different from query parameters redirect we don't want to redirect based on query parameters we just want to keep them after the redirect. Thank you

This would speed up development times and help Gatsby compete with other frameworks like Next.js

Hi everyone, I need to return a 410 statuscode with the same behavior as 404/403/451/500 for pages like spam. We think a 410 is more accurate, which shows that we intentionally removed it and do not crawl. Nowadays, statusCode just works with 404,403,451,500 code. If we use other codes the status code returned is 302, and the URL in the browser location bar changes to the toPath. Please, we are so interested in use it to improve our SEO.

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.