From f2d3d1db9a389409018c7579052be31c04537e7d Mon Sep 17 00:00:00 2001
From: Andy Coates <8012398+big-andy-coates@users.noreply.github.com>
Date: Wed, 16 Aug 2023 14:14:20 +0100
Subject: [PATCH] Add example of using  `DEPENDENCY_GRAPH_INCLUDE_PROJECTS` to
 docs

Users will currently need to spend some time working out the required regex when using `DEPENDENCY_GRAPH_INCLUDE_PROJECTS`. Providing an example will get users up to speed quicker.

Signed-off-by: Andy Coates <8012398+big-andy-coates@users.noreply.github.com>
---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 501ca45..430bf74 100644
--- a/README.md
+++ b/README.md
@@ -461,7 +461,7 @@ You can provide this value via the `DEPENDENCY_GRAPH_INCLUDE_PROJECTS` environme
 To restrict which Gradle configurations contribute to the report, you can filter configurations by name using a regular expression.
 You can provide this value via the `DEPENDENCY_GRAPH_INCLUDE_CONFIGURATIONS` environment variable or system property.
 
-Example of a simple workflow that limits the dependency graph to `RuntimeClasspath` configuration:
+Example of a simple workflow that limits the dependency graph to `RuntimeClasspath` configuration and to exclude `buildSrc` dependencies:
 ```yaml
 name: Submit dependency graph
 on:
@@ -481,6 +481,8 @@ jobs:
         dependency-graph: generate-and-submit
     - name: Run a build, generating the dependency graph from 'RuntimeClasspath' configurations
       run: ./gradlew build -DDEPENDENCY_GRAPH_INCLUDE_CONFIGURATIONS=RuntimeClasspath
+      env:
+        DEPENDENCY_GRAPH_INCLUDE_PROJECTS: "^:(?!buildSrc).*"
 ```
 
 ### Gradle version compatibility