Skip to content

Commit 19003bc

Browse files
resolve linters
1 parent 4ecf29f commit 19003bc

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/content/docs/infrastructure/host-integrations/host-integrations-list/github-integration.mdx

+3-3
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ freshnessValidatedDate: 2024-10-29
88
---
99

1010

11-
Implementing a New Relic Service Catalog can unlock considerable benefits, but at present, it requires a considerable investment of time and resources. You have to take care of team orchestration, user provisioning, role assignments, and entity ownership delineation, which create a significant threshold for entry. To alleviate this challenge, we suggest the adoption of an automation solution that capitalizes on existing team configurations and relationships maintained in external systems such as GitHub. This simplifies the initial configuration, dramatically lessen the required effort, and accelerates the adoption of the New Relic Service Catalog, making its powerful insights and organization tools more accessible to users.
11+
Implementing a New Relic Service Catalog can unlock considerable benefits, but at present, it requires a considerable investment of time and resources. You have to take care of team orchestration, user provisioning, role assignments, and entity ownership delineation, which create a significant threshold for entry. To ease this challenge, we suggest the adoption of an automation solution that capitalizes on existing team configurations and relationships maintained in external systems such as GitHub. This simplifies the initial configuration, dramatically lessen the required effort, and accelerates the adoption of the New Relic Service Catalog, making its powerful insights and organization tools more accessible to users.
1212

1313
<img
1414
title="GitHub Integration dashboard"
@@ -22,7 +22,7 @@ After setting up our GitHub integration, see your data of teams, repos and users
2222

2323
## Prerequisites [#prerequisites]
2424

25-
Users need to ensure that they are logged in to their GitHub accounts. This needs to be the same GitHub account in which they want to install the GitHub app that New Relic will be providing during installation step.
25+
Users need to ensure that they're logged in to their GitHub accounts. This needs to be the same GitHub account in which they want to install the GitHub app that New Relic will be providing during installation step.
2626

2727

2828
## Set up the GitHub integration [#set-up-github]
@@ -51,7 +51,7 @@ Users can enable it for importing all the items mentioned in the Power Service C
5151

5252
As a next step of installation, we need to click on the install button. Then we get redirected to the GitHub App installation page. This app is provided by New Relic to help fetch the user's GitHub account related information.
5353

54-
Once the installation is complete, we will see the result page which will dynamically list down the retrieved GitHub data related to teams, repos, pull requests and deployments. It will take some time to fetch the complete inforamtion, hence the page will keep refreshing after every 10 seconds till we have the power service catalog ready.
54+
Once the installation is complete, we will see the result page which will dynamically list down the retrieved GitHub data related to teams, repos, pull requests and deployments. It will take some time to fetch the complete inforamtion, hence the page will keep refreshing after every 10 seconds till we've the power service catalog ready.
5555

5656
The result obtained will look like the below:
5757

0 commit comments

Comments
 (0)