From 0faae6be50d7f1022df15b79b8c9fa5c556ff8b3 Mon Sep 17 00:00:00 2001 From: Gabriel Feo Date: Fri, 12 Apr 2024 13:11:33 +0100 Subject: [PATCH] Fix link to doc section --- docs/setup-gradle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/setup-gradle.md b/docs/setup-gradle.md index fa7fcb8..66f6e31 100644 --- a/docs/setup-gradle.md +++ b/docs/setup-gradle.md @@ -8,7 +8,7 @@ It is possible to directly invoke Gradle in your workflow, and the `actions/setu However, the `setup-gradle` action offers a several advantages over this approach: -- Easily [configure your workflow to use a specific version of Gradle](#choose-a-specific-gradle-version) using the `gradle-version` parameter. Gradle distributions are automatically downloaded and cached. +- Easily [configure your workflow to use a specific version of Gradle](#build-with-a-specific-gradle-version) using the `gradle-version` parameter. Gradle distributions are automatically downloaded and cached. - More sophisticated and more efficient caching of Gradle User Home between invocations, compared to `setup-java` and most custom configurations using `actions/cache`. [More details below](#caching-build-state-between-jobs). - Detailed reporting of cache usage and cache configuration options allow you to [optimize the use of the GitHub actions cache](#optimizing-cache-effectiveness). - [Generate and Submit a GitHub Dependency Graph](#github-dependency-graph-support) for your project, enabling Dependabot security alerts.