Эта версия GitHub Enterprise Server была прекращена 2024-09-25. Исправления выпускаться не будут даже при критических проблемах безопасности. Для повышения производительности, повышения безопасности и новых функций выполните обновление до последней версии GitHub Enterprise Server. Чтобы получить справку по обновлению, обратитесь в службу поддержки GitHub Enterprise.

Включение графа зависимостей для предприятия

Вы можете разрешить пользователям определять зависимости проектов, включив граф зависимостей.

Кто может использовать эту функцию?

Site administrators can enable the dependency graph.

В этой статье

About the dependency graph

The dependency graph is a summary of the manifest and lock files stored in a repository and any dependencies that are submitted for the repository using the dependency submission API. For each repository, it shows dependencies, the ecosystems and packages it depends on.

GitHub Enterprise Server does not retrieve license information for dependencies, and does not calculate information about dependents, the repositories and packages that depend on a repository. For more information, see About the dependency graph

After you enable the dependency graph, users will have access to the dependency review feature. Dependency review helps you understand dependency changes and the security impact of these changes at every pull request. For more information, see "About dependency review."

After you enable the dependency graph for your enterprise, you can enable Dependabot to detect insecure dependencies in your repository and automatically fix the vulnerabilities. For more information, see Enabling Dependabot for your enterprise.

You can enable the dependency graph via the Management Console or the administrative shell. We recommend using the Management Console unless your instance uses clustering.

Enabling the dependency graph via the Management Console

If your instance uses clustering, you cannot enable the dependency graph with the Management Console and must use the administrative shell instead. For more information, see Enabling the dependency graph via the administrative shell.

  1. Sign in to your GitHub Enterprise Server instance at http(s)://HOSTNAME/login.

  2. From an administrative account on GitHub Enterprise Server, in the upper-right corner of any page, click .

  3. If you're not already on the "Site admin" page, in the upper-left corner, click Site admin.

  4. In the " Site admin" sidebar, click Management Console.

  5. In the "Settings" sidebar, click Security.

  6. Under "Security," select Dependency graph.

  7. Under the "Settings" sidebar, click Save settings.

    Note

    Saving settings in the Management Console restarts system services, which could result in user-visible downtime.

  8. Wait for the configuration run to complete.

  9. Click Visit your instance.

Enabling the dependency graph via the administrative shell

  1. Sign in to your GitHub Enterprise Server instance at http(s)://HOSTNAME/login.

  2. In the administrative shell, enable the dependency graph:

    ghe-config app.dependency-graph.enabled true

    Note

    For more information about enabling access to the administrative shell via SSH, see Accessing the administrative shell (SSH).

  3. Apply the configuration.

    ghe-config-apply

  4. Return to GitHub Enterprise Server.