Update Dependency Cache

Your first CI run completed successfully, but it did not restore the cache from GitHub Actions Cache. To optimize future runs, merge your pull request into the main branch to automatically update the dependency cache. This way, subsequent workflow executions in other branches will benefit from the cache created in the main branch, improving speed and efficiency.

1. Under your remote repository,

• Select Pull requests tab.
• Choose your opened request first config.

2. Click Merge pull request.

3. Click Confirm merge.

4. Click Delete branch.

5. Head over to the Actions tab, and you will see that the Update dependency cache workflow has been triggered. Click on the running workflow to view more details.

6. You might notice that the Update dependency cache job completed in about 30 seconds. Click on the Update dependency cache job to explore the details.

7. Expand the Cache dependencies step dropdown. You will see the message Cache not found for input keys since this is the first run of your Update dependency cache workflow, and no cache is restored from refs/pull/1/merge.

8. Open the Update cache step dropdown. Here, you will see that this step is responsible for downloading all the required dependencies for the application since there is no cache hit in the previous step.

9. Click Post Cache dependencies step dropdown. This step should perform the cache saving as it specifies Cache saved successfully and Cache saved with key.

10. Check the GitHub Actions Cache to view the cache for the main branch. Now, other branches should be able to restore their dependencies from this cache, as long as the specific key remains unchanged.