add new ea github comment feature (#7510)

* add new ea github comment feature

* style(lint): Auto commit lint changes

* Update src/docs/product/accounts/early-adopter-features/index.mdx

* Update src/docs/product/integrations/source-code-mgmt/github/index.mdx

* Update src/docs/product/integrations/source-code-mgmt/github/index.mdx

* Update src/docs/product/accounts/early-adopter-features/index.mdx

* Update src/docs/product/integrations/source-code-mgmt/github/index.mdx

* style(lint): Auto commit lint changes

---------

Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>

src/docs/product/integrations/source-code-mgmt/github/index.mdx

@@ -219,6 +219,16 @@ You can also resolve issues with pull requests by including `fixes <SENTRY-SHORT
 
 When Sentry sees this, we’ll automatically annotate the matching issue with a reference to the commit or pull request, and, later, when that commit or pull request is part of a release, we’ll mark the issue as resolved. The commit must be associated with a release. Otherwise, if the commit is squashed, Sentry won’t know when the commit has been released, and the issue may never be marked as a regression. With GitHub, we recommend using `fixes <SENTRY-SHORT-ID>` in the body of your pull request that is going to be merged to your main branch.
 
+### Get Sentry Comments on Suspect Pull Requests
+
+If a recently merged pull request is suspected of causing an issue, Sentry will comment on it as in the example below.
+
+![Sentry comment on suspect pull request in GitHub](sentry-github-pr-comment.png)
+
+This feature will be automatically enabled for you once your GitHub integration has been set up. To disable it, go to **Settings > Integrations > GitHub** and toggle it off.
+
+![How to disable Sentry comments on GitHub pull requests](github-org-settings.png)
+
 ### Stack Trace Linking
 
 <Note>