docs-website for github integration #19286
Conversation
|
|
|
Hi @dinesh-newrelic 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). |
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
ubanerjeeNR
added
content
| src="/images/github-integration-progress.webp" | ||
| /> | ||
|
|
||
| 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. |
There was a problem hiding this comment.
Next, click Install. The GitHub App installation page loads. New Relic provides this app to fetch the GitHub account information of a user.
|
|
||
| ## Service Catalog Details [#service-catalog-details] | ||
|
|
||
| In this installation step, we will be asked to enable/disable the Power Service catalog option. Power Service catalog provides the users the ability to import all the data related to Teams, Repositories, Pull Request, Pull Request Review and Deployment. |
There was a problem hiding this comment.
In this step, you have to enable or disable the Power Service catalog option. This option provides users the ability to import all data related to teams, repositories, pull requests, pull request reviews, and deployments.
| --- | ||
|
|
||
|
|
||
| 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. |
There was a problem hiding this comment.
Implementing a New Relic Service Catalog can unlock considerable benefits, but it requires considerable time and resources. You have to take care of team orchestration, user provisioning, role assignments, and entity ownership delineation. These create a significant threshold for entry. To ease this challenge, consider an automation solution that capitalizes on existing team configurations and relationships maintained in external systems such as GitHub. This simplifies the initial configuration and accelerates the adoption of the New Relic Service Catalog.
Previous pr: #19113