feat(commit-context): Add documentation about commit context fallback (#6466)

* Add documentation about commit context fallback

* Apply suggestions from code review

Co-authored-by: Liza Mock <liza.mock@sentry.io>

---------

Co-authored-by: Liza Mock <liza.mock@sentry.io>

Author: snigdhas

src/docs/product/accounts/getting-started/index.mdx

@@ -56,7 +56,7 @@ Learn more about setting up alerts with integrations in [Alert Routing With Inte
 
 When you enable an integration with your source code management (SCM) provider, Sentry will analyze your commit data to:
 
-1. Identify **suspect commits** that likely introduced an error ([GitHub and GitLab only](/product/integrations/#source-code-management)).
+1. Identify **suspect commits** that likely introduced an error.
 1. **Suggest assignees** who can best resolve the error, based on the suspect commits and your [codeowners file](/product/issues/issue-owners/#code-owners).
 1. Mark an issue as **Resolved via Commit or PR** to stop notifications about similar errors in past releases and notify you of a regression.
 1. Link a Sentry issue to a new or existing issue in your integrated [issue tracking](#33-issue-tracking) solution.

src/docs/product/issues/suspect-commits/index.mdx

@@ -22,7 +22,7 @@ Suspect commits and suggested assignees are then displayed on the **Issue Detail
 
 ## Enable Suspect Commits
 
-This process assumes that source maps — or your platform-specific files for mapping transformed source code to the original source — have been uploaded (check out the docs for your [specific platform](/platforms/)).
+In order to see suspect commits, you have to first upload source maps, (or your platform-specific files for mapping transformed source code to the original source). Check out the docs for your [specific platform](/platforms/)) to learn more. Note, that Sentry may not display suspect commits that were committed prior to your integration being set up.
 
 ### 1. Connect a Repository Using Integrations
 
@@ -61,10 +61,18 @@ Sentry will automatically try to set up code mappings on Python and JavaScript p
 
 The first frame in the stack trace is considered suspect when looking at them top-down. If the first frame is not in-app, the next frame is considered suspect.
 
+## Suspect Commits Without Integrations
+
+You can send us your commit data [manually](/product/releases/associate-commits/) if:
+- You don’t want Sentry to connect to your repository.
+- Your organization doesn't have a GitHub or Gitlab integration.
+- Your integration has gotten disconnected.
+
+Sentry will attempt to find suspect commits via your Github or Gitlab integration by default. If this fails and you've set up the manual process, Sentry will fall back to using the release commit data to find suspect commits. 
+
 ## Missing Suspect Commits
 
 There are a few reasons why an issue might not have suspect commits:
-- Your GitHub or GitLab integration isn't set up or has become disconnected.
 - The issue doesn't have a stack trace or doesn't have any in-app frames.
 - The stack trace doesn't have any in-app frames that match the code mappings.
 - The code mappings for the project are incorrect.