title | intro | redirect_from | versions | type | topics | shortTitle | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Configuring the dependency graph |
You can allow users to identify their projects' dependencies by enabling the dependency graph. |
|
|
how_to |
|
Configure dependency graph |
{% data reusables.dependabot.about-the-dependency-graph %}
For more information, see "AUTOTITLE."
{% ifversion fpt or ghec %}
To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private {% ifversion ghec %}and internal {% endif %}repositories. For more information on viewing the dependency graph, see "AUTOTITLE."
{% data reusables.dependency-submission.dependency-submission-link %}
{% endif %}
{% ifversion ghes %}
{% data reusables.dependabot.ghes-enabling-dependency-graph %}{% endif %}
{% ifversion ghec %}
{% endif %}{% ifversion fpt %}
{% endif %}{% ifversion fpt or ghec %} {% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo %}
{% endif %}
When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% ifversion fpt or ghec %} and every push to other repositories in the graph{% endif %}.
{% ifversion ghes %} {% data reusables.dependency-submission.dependency-submission-link %} {% endif %}
{%- ifversion maven-transitive-dependencies %}