benchmark-action / benchmark-action/github-action-benchmark

A warning should not be issued when the cache does not exist.

Open
#193 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
1.3k
Forks
184
PR merge metrics
No merged PRs in 30d

Description

When this action is first executed on a branch, it is natural that the cache does not exist.
However, these actions are currently displaying a warning and outputting an error.
image
Like @actions/cache, it prints that there is no cache, but this should not be marked as a warning.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.