Skip to content

Commit

Permalink
Update index.mdx
Browse files Browse the repository at this point in the history
Add suggestions
  • Loading branch information
vivianyentran authored Dec 6, 2023
1 parent f9f571a commit 2f16711
Showing 1 changed file with 6 additions and 4 deletions.
10 changes: 6 additions & 4 deletions src/docs/product/integrations/source-code-mgmt/github/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -9,15 +9,17 @@ redirect_from:
- /integrations/github-enterprise/
- /integrations/github/
description: "Learn more about Sentry's GitHub integration and how it can track and resolve bugs faster by using data from your GitHub commits, and streamline your triaging process by creating a GitHub issue directly from Sentry."
---

Track and resolve bugs faster by using data from your GitHub commits, and streamline your triaging process by creating a GitHub issue directly from Sentry.

<Note>

If you're not sure which GitHub integration you need to configure, please take a look at the URL. The https://github.com/org-name is usually for GitHub-hosted accounts. The self-hosted GitHub Enterprise accounts typically have URLs that look more like this: https://github.org-name.com (or some other customization of the domain). If that's the case, you should configure the non-Enterprise GitHub integration.
If you're not sure which GitHub integration you need to configure, please take a look at the URL. URLs like `https://github.com/org-name` are usually for GitHub-hosted accounts and should use the regular GitHub (not GitHub Enterprise) integration. See [Install](#install) for more details.

</Note>
---
Self-hosted GitHub Enterprise accounts typically have URLs that look more like `https://github.org-name.com` (or some other customization of the domain). In this

Track and resolve bugs faster by using data from your GitHub commits, and streamline your triaging process by creating a GitHub issue directly from Sentry.
</Note>

## Install

Expand Down

0 comments on commit 2f16711

Please sign in to comment.