From 49393e6675686c0d10cf8868c6863a24ed691c83 Mon Sep 17 00:00:00 2001 From: Daz DeBoer Date: Wed, 31 Jan 2024 12:13:00 -0700 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 4fa6760..18cc1ff 100644 --- a/README.md +++ b/README.md @@ -98,7 +98,7 @@ Note that no dependency graph will be generated when configuration state is load | 8.0 - 8.0.2 | ✅ | :x: | | 8.1+ | ✅ | ✅ | -## Using the plugin standalone project +## Using the plugin to generate dependency reports As well as the `GitHubDependencyGraphPlugin`, which is tailored for use by the [gradle/actions/dependency-submission](https://github.com/gradle/actions/tree/main/dependency-submission) GitHub Action, this repository also provides the `SimpleDependencyGraphPlugin`, which generates dependency-graph outputs in simple text format. @@ -124,7 +124,7 @@ and then execute the task to resolve all dependencies in your project: You'll find the generated files in `build/dependency-graph-snapshots`. -### Determine the underlying source of dependencies +### Using dependency reports to determine the underlying source of a dependency After generating the dependency reports as described, it is possible to determine the dependency source by: