Caching Mechanism described

Author: WorkOfStan

.github/workflows/polish-the-code.yml

@@ -26,7 +26,7 @@ jobs:
     timeout-minutes: 10
     steps:
       - name: Invoke the Prettier fix
-        uses: WorkOfStan/prettier-fix@v1.1.1
+        uses: WorkOfStan/prettier-fix@v1.1.2
         with:
           commit-changes: true
 

README.md

@@ -50,3 +50,12 @@ permissions:
 | Output        | Description                         |
 | ------------- | ----------------------------------- |
 | `branch-name` | The name of the branch created/used |
+
+## Caching Mechanism
+
+To optimize execution time, the `vendor` folder is cached, allowing dependencies to be reused across workflow runs. The cache key is generated based on:
+
+- `composer.json` – to track dependency changes.
+- The runner's OS and PHP version – to account for environment-specific variations.
+
+This approach enables cache sharing across branches. However, if the `composer.json` file in the referenced branch (e.g., `dev`) changes, it's recommended to **invalidate the cache** to ensure a fresh `vendor` folder is built from scratch.