feat(codeowners): Add EA docs for Code Owners (#3931)

Author: NisanthanNanthakumar

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

@@ -247,6 +247,20 @@ Stack trace linking takes you from a file in your Sentry stack trace to that sam
      1. If the filename in your Sentry stack trace frame doesn't match the path to your source code, you will need to replace the **stack_root** part of the filename with your **source_root** to make the filename match the source code path.
         - ex. For example, to get `src/code.py` to match `code.py` when the source code path is `https://github.com/MeredithAnya/testing/blob/main/code.py`, change the **stack trace root** to be set as `src/`, and leave **source code root** empty.
 
+### Code Owners
+
+<Note>
+
+This feature is available only if you're in the Early Adopter program. Features available to Early Adopters are still in-progress and may have bugs. We recognize the irony. If you’re interested in being an Early Adopter, you can turn your organization’s Early Adopter status on/off in General Settings. This will affect all users in your organization and can be turned back off just as easily.
+
+Let us know if you have feedback: [[email protected]](mailto:[email protected]).
+
+</Note>
+
+Import your existing GitHub CODEOWNERS files to automatically assign Sentry issues and route alerts to the responsible individuals and teams.
+
+For more details, see the full documentation for [Code Owners](/product/issues/issue-owners/#code-owners).
+
 ### GitHub Single Sign-On
 
 Single Sign-On (or SSO) allows you to manage your organization’s entire membership via a third-party provider.

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

@@ -147,6 +147,19 @@ Stack trace linking takes you from a file in your Sentry stack trace to that sam
       1. If the file path in your Sentry stack trace frame doesn't match the path to your source code, you will need to replace the **stack_root** part of the file path with your **source_root** to make the file path match the source code path.
          * ex. For example, to get `src/code.py` to match `code.py` when the source code path is `https://gitlab.com/murdith-group/issa-project/-/blob/main/code.py`, change the **stack trace root** to be set as `src/`, and leave **source code root** empty.
 
+### Code Owners
+
+<Note>
+
+This feature is available only if you're in the Early Adopter program. Features available to Early Adopters are still in-progress and may have bugs. We recognize the irony. If you’re interested in being an Early Adopter, you can turn your organization’s Early Adopter status on/off in General Settings. This will affect all users in your organization and can be turned back off just as easily.
+
+Let us know if you have feedback: [[email protected]](mailto:[email protected]).
+
+</Note>
+
+Import your existing GitLab CODEOWNERS files to automatically assign Sentry issues and route alerts to the responsible individuals and teams.
+
+For more details, see the full documentation for [Code Owners](/product/issues/issue-owners/#code-owners).
 
 ## Troubleshooting
 

src/docs/product/issues/issue-owners/code_owners.png

@@ -58,6 +58,43 @@ You can also add a rule from the Issue Details page:
 
 When you create a rule from the Issue Details page, you'll see some suggested paths and URLs based on the events in the issue. Note that [sentry.io](https://sentry.io) doesn't suggest tags.
 
+### Code Owners
+
+<Note>
+
+This feature is available only if you're in the Early Adopter program. Features available to Early Adopters are still in-progress and may have bugs. We recognize the irony. If you’re interested in being an Early Adopter, you can turn your organization’s Early Adopter status on/off in General Settings. This will affect all users in your organization and can be turned back off just as easily.
+
+Let us know if you have feedback: [[email protected]](mailto:[email protected]).
+
+</Note>
+
+![Code Owners in UI](code_owners.png)
+
+Import your CODEOWNERS file and use it alongside your Ownership Rules to assign Sentry issues. You can import and incrementally add the mappings between your source control teams/users to Sentry Teams/Users using [External Team/User Mappings](/product/issues/issue-owners/#external-teamuser-mappings). Sentry will automatically ignore rules that are missing team/user mappings.
+
+This feature supports GitHub and GitLab CODEOWNERS file syntax with the following exceptions:
+ - Escaping a pattern starting with `#` using `\` so it is treated as a pattern and not a comment
+ - Using `!` to negate a pattern
+ - Using `[ ]` to define a character range
+ - [GitLab Premium syntax](https://docs.gitlab.com/ee/user/project/code_owners.html#code-owners-sections)
+ - [GitHub CODEOWNERS syntax exceptions](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-code-owners#syntax-exceptions)
+
+### External Team/User Mappings
+
+<Note>
+
+This feature is available only if you're in the Early Adopter program. Features available to Early Adopters are still in-progress and may have bugs. We recognize the irony. If you’re interested in being an Early Adopter, you can turn your organization’s Early Adopter status on/off in General Settings. This will affect all users in your organization and can be turned back off just as easily.
+
+Let us know if you have feedback: [[email protected]](mailto:[email protected]).
+
+</Note>
+
+![External team mappings for Github/Gitlab](external_team_mappings.png)
+
+![External user mappings for Github/Gitlab](external_user_mappings.png)
+
+Create external team/user mappings for your GitHub/GitLab teams and users by navigating to **Settings > Integrations > GitHub/GitLab > [Configuration] > Team Mappings/User Mappings**.
+
 ### Suggested Assignees
 
 On the Issue Details page, you'll see suggested assignees based on ownership rules matching the event you're looking at (by default, the Issue Details page shows the latest event). Suggested assignees can also be based on [suspect commits](/product/releases/suspect-commits/). You can assign the _issue_ to a suggested assignee by clicking on the suggestion. An event can have multiple suggested assignees if it matches multiple ownership rules.