GPT4ができそうな方法を提案したけど結局できなかった話
Git LFSに保存していたキャッシュファイルを別の方法にしたくてGPT4に聞いた 「Github Actionsで作成したキャッシュファイルを置いたり取得したりするのに最適な方法は？次回のアクションでそのファイルにアクセスしたいのですが、履歴を残す必要はありません。」
nishio.icon What is the best way to put and get cache file which created in Github Actions. I want to access the file in next time action, but no need to keep history.
GPT.icon GitHub Actions provide built-in support for caching dependencies and build outputs to improve workflow execution time. However, GitHub's cache is not meant to be a way to share data between jobs or workflows; it's meant to be used to speed up installing dependencies that you'd otherwise have to fetch from a remote server. As such, it's subject to a number of limitations and considerations:
Cache storage is limited to 5 GB per repository.
Not all types of files can be cached.
...
However, if you're looking to share data between jobs or between different runs of the workflow, you might want to consider using GitHub's artifact support.
Artifacts allow you to persist data between jobs in a workflow, and they can be used to store data for use in a later job. They're also accessible after the workflow is completed, so they can be downloaded manually if needed.
Here is an example of how to use them:
...
できそうに思うじゃん？
nishio.icon I want to store data on a run of a workflow, then on next day I want to use the stored data in the same workflow.
gpt.icon GitHub Actions does not directly provide a way to persist data between separate workflow runs. However, there are several ways you can achieve this:
nishio.icon Can I share artifact files between different runs of the workflow?
gpt.icon As of my knowledge cutoff in September 2021, you cannot directly share artifact files between different runs of a GitHub Actions workflow. Artifacts are tied to the specific workflow run that created them, and they are not accessible across different workflow runs.
できないじゃん！