840: Fix configuration name in dependency filtering section

Fixes: https://github.com/gradle/gradle-build-action/issues/840
This commit is contained in:
Andy Coates 2023-08-16 12:20:58 +01:00 committed by GitHub
parent e3028deccc
commit bd7dc8ec7e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -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:
```yaml
name: Submit dependency graph
on:
@ -479,8 +479,8 @@ jobs:
uses: gradle/gradle-build-action@v2
with:
dependency-graph: generate-and-submit
- name: Run a build, generating the dependency graph from 'RuntimeClasspath' configurations
run: ./gradlew build -DDEPENDENCY_GRAPH_INCLUDE_CONFIGURATIONS=RuntimeClasspath
- name: Run a build, generating the dependency graph from 'runtimeClasspath' configurations
run: ./gradlew build -DDEPENDENCY_GRAPH_INCLUDE_CONFIGURATIONS=runtimeClasspath
```
### Gradle version compatibility