From 1b1bbe1085cb6ab21b5b19b7bebc091a9430026a Mon Sep 17 00:00:00 2001
From: priya-kinthali <147703874+priya-kinthali@users.noreply.github.com>
Date: Tue, 20 Jan 2026 08:16:13 +0530
Subject: [PATCH] readme update (#972)

---
 README.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/README.md b/README.md
index 7addc9a4..8e21cd95 100644
--- a/README.md
+++ b/README.md
@@ -156,6 +156,11 @@ steps:
       sub-project/**/gradle-wrapper.properties
 - run: ./gradlew build --no-daemon
 ```
+Using the `cache: gradle` provides a simple and effective way to cache Gradle dependencies with minimal configuration.
+
+For projects that require more advanced `Gradle` caching features, such as caching build outputs, support for Gradle configuration cache, encrypted cache storage, fine-grained cache control (including options to enable or disable the cache, set it to read-only or write-only, perform automated cleanup, and define custom cache rules), or optimized performance for complex CI workflows, consider using [`gradle/actions/setup-gradle`](https://github.com/gradle/actions/tree/main/setup-gradle).  
+
+For setup details and a comprehensive overview of all available features, visit the [setup-gradle documentation](https://github.com/gradle/actions/blob/main/docs/setup-gradle.md).
 
 #### Caching maven dependencies
 ```yaml