Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache octokit in GitHub workflows #9330

Merged

Conversation

jimchamp
Copy link
Collaborator

Closes #9250

Caches @octokit/action for applicable GitHub workflows.

Technical

Caches octokit in the same way that it is cached in #9311. The key is reused for each octokit cache entry. If additional JS dependencies are added to any workflow that caches octokit, the cache key may need to be updated for that particular workflow.

Testing

Merge this into your forked repo's master branch, then trigger one of the workflows. If there is no cache hit, wait until the workflow is finished, then trigger it again. Expect the npm install step to be skipped on the second run.

Screenshot

Stakeholders

@jimchamp
Copy link
Collaborator Author

I wonder if the stale_assignee_digest workflow can be removed?

@mekarpeles mekarpeles merged commit ab0d7a6 into internetarchive:master May 24, 2024
4 checks passed
@mekarpeles mekarpeles self-assigned this May 24, 2024
@jimchamp jimchamp deleted the 9250/feature/cache-octokit branch May 30, 2024 19:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cache Octokit for better workflow performance
2 participants