Merge branch 'master' into smarter-search

Author: a-hariti

app/[[...path]]/page.tsx

@@ -209,6 +209,8 @@ export async function generateMetadata(props: MetadataProps): Promise<Metadata>
       ? [{url: `${previewDomain ?? domain}/og.png`, width: 1200, height: 630}]
       : [];
 
+  let noindex: undefined | boolean = undefined;
+
   const rootNode = await getDocsRootNode();
 
   if (params.path) {
@@ -227,6 +229,8 @@ export async function generateMetadata(props: MetadataProps): Promise<Metadata>
       if (pageNode.frontmatter.customCanonicalTag) {
         customCanonicalTag = formatCanonicalTag(pageNode.frontmatter.customCanonicalTag);
       }
+
+      noindex = pageNode.frontmatter.noindex;
     }
   }
 
@@ -253,5 +257,6 @@ export async function generateMetadata(props: MetadataProps): Promise<Metadata>
     alternates: {
       canonical,
     },
+    robots: noindex ? 'noindex' : undefined,
   };
 }

develop-docs/application-architecture/feedback-architecture.mdx

@@ -21,7 +21,7 @@ the [User Feedback Widget](https://docs.sentry.io/product/user-feedback/#user-fe
 to the JavaScript SDK. It allows adding more information, for example tags,
 release, url, etc.
 
-`USER_REPORT_ENVELOPE`: [The older format](/sdk/data-model/envelope-items/#user-report) with name/email/comments, that requires
+`USER_REPORT_ENVELOPE`: [The older format](/sdk/data-model/envelope-items/#user-report---deprecated) with name/email/comments, that requires
 `event_id` to link a Sentry error event.
 
 `USER_REPORT_DJANGO_ENDPOINT`: [The deprecated Web API](https://docs.sentry.io/api/projects/submit-user-feedback/)
@@ -186,7 +186,7 @@ graph TD
 
 ### Envelopes
 
-User reports are also sent to Relay in envelope format, item type [user_report](/sdk/data-model/envelope-items/#user-report).
+User reports are also sent to Relay in envelope format, item type [user_report](/sdk/data-model/envelope-items/#user-report---deprecated).
 
 The SDK function that sends these is `captureUserFeedback`.
 
@@ -231,10 +231,9 @@ graph TD
 
   subgraph Sentry
     issues_endpoint["/issues"]
-    issues_endpoint --> |"GET"| ui["Feedback UI (/feedback)"]
+    issues_endpoint --> |"GET"| feedback_ui["Feedback UI (/feedback)"]
     report_endpoint["/user-feedback"]
-    report_endpoint --> |"GET"| report_ui["Issue Details UI > User Feedback"]
-    issues_endpoint --> |"GET"| report_ui
+    report_endpoint --> |"GET"| issues_ui["Issue Details UI > User Feedback"]
   end
 
   postgres --> |"queries"| report_endpoint

develop-docs/getting-started/index.mdx

@@ -4,15 +4,10 @@ description: This documentation serves as reference points for developing agains
 sidebar_order: 1
 ---
 
-## Getting Started
+We recommend going through the [engineering practices](/engineering-practices) and our [development philsophy](/getting-started/philosophy/) before contributing a change to Sentry.
 
-We recommend going through the general documentation before contributing a change to Sentry.
 
-- <Link to="/getting-started/philosophy/">Development Philosophy</Link> (and <Link to="/sdk/philosophy/">SDK Development Philosophy</Link>)
-- <Link to="/development/commit-messages/">Commit Messages</Link>
-- <Link to="/development/code-review/">Code Review</Link>
-- <Link to="/development/environment/">Environment</Link>
-- <Link to="/development/workflow/">Workflow</Link>
-- <Link to="/application/architecture/">Application Architecture</Link>
+<DevDocsCardGrid />
+
 
 You can also take a glance at the [Sentry Dockerfile](https://github.com/getsentry/sentry/blob/master/self-hosted/Dockerfile) for more information on how the Sentry server is configured, including its system dependencies.

develop-docs/ingestion/relay/transaction-span-ratelimits.mdx

@@ -69,19 +69,19 @@ Relay stage: customer managed, PoP-Relay or Processing-Relay. Until spans are ex
 should count the contained spans and generate an outcome with the contained span quantity + 1, for the segment span
 which would be generated from the transaction itself.
 
-<Note>
+<Alert>
 While it is desirable to have span counts correctly extracted from dropped transactions, it may not be feasible
 to do so at any stage of the processing pipeline. For example, it may not be possible to do so (malformed transactions)
 or simply too expensive to compute.
-</Note>
+</Alert>
 
 After spans have been extracted, the transaction is no longer a container of span items and just represents itself,
 thus, a dropped transaction with spans already extracted only generates outcomes for the total transactions and
 indexed transaction categories.
 
-<Note>
+<Alert>
 Span quotas are equivalent to transactions quotas, so all the above also applies for a span quota.
-</Note>
+</Alert>
 
 
 ## Examples

develop-docs/integrations/azuredevops/index.mdx

@@ -25,12 +25,12 @@ When configuring the app, use the following values:
 | Supported account types         | Accounts in any organizational directory |
 | Redirect URI                    | `{YOUR_DOMAIN}/extensions/vsts/setup`                                                              |
 
-<Note>
+<Alert>
 
 Take note of your App ID as we'll need it later.
 ![App ID](./app-id.png)
 
-</Note>
+</Alert>
 
 Next go to Manager -> API Permissions to add the following permissions:
 * Azure DevOps (`vso.code`, `vso.graph`, `vso.work_item`, `vso.service_endpoint`)

develop-docs/integrations/bitbucket.mdx

@@ -0,0 +1,29 @@
+---
+title: Bitbucket Integration
+sidebar_title: Bitbucket
+---
+
+## Prerequisites
+
+#### Create a Bitbucket "product"
+
+To use Sentry’s Bitbucket integration you’ll need to create a Bitbucket "product" if you don’t already have one.
+
+Go to [Bitbucket's Admin Console](http://admin.atlassian.com/) and click on __Add Product__. and select __Bitbucket__. Name your Bitbucket instance and click __Create__.
+
+![Add Product](./add-product.png)
+
+#### Create a Bitbucket Repo
+
+Next, you'll need to create a Bitbucket repository. Click on __Create repository__ and fill in the details. You should now see your new repository in the list of repositories.
+
+![Create Repository](./create-repo.png)
+
+
+## Create a Bitbucket App
+
+To use Sentry’s Bitbucket integration you’ll need to create a Bitbucket app. Navigate to [Bitbucket Apps](https://bitbucket.org/account/user/apps/create) and click __Create__.
+Ensure [developer mode](https://support.atlassian.com/bitbucket-cloud/docs/enable-bitbucket-cloud-development-mode/) is enabled in your Atlassian account.
+
+
+Follow our [documentation on configuring the Bitbucket integration](https://docs.sentry.io/product/integrations/bitbucket/#configure) to use the integration.

develop-docs/integrations/bitbucket/add-product.png

@@ -5,10 +5,10 @@ sidebar_title: GitHub
 
 ## Create a GitHub App
 
-To configure the GitHub integration you'll need to create a GitHub app and obtain credentials.
+To configure the GitHub integration you'll need to create a GitHub app and obtain credentials. Installation will fail if your Github App's name contains spaces.
 
 <Alert level="warning">
-  The GitHub Org Slug must not contain any spaces.
+  The GitHub App name and GitHub Org Slug must not contain any spaces.
 </Alert>
 
 <CreateGitHubAppForm url="https://github.com/organizations/:org/settings/apps/new?name=:org-Sentry-Integration&public=false&members=read&emails=read&administration=read&contents=read&issues=write&pull_requests=write&repository_hooks=write&url=:url-prefix&callback_url=:url-prefix%2Fauth%2Fsso%2F&setup_url=:url-prefix%2Fextensions%2Fgithub%2Fsetup%2F&webhook_url=:url-prefix%2Fextensions%2Fgithub%2Fwebhook%2F&events[]=push&events[]=pull_request&webhook_active=true" defaultOrg="your-organization" defaultUrlPrefix="https://your-sentry-url-prefix.com" />