AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
How to delete all of my items off shop tagr11/19/2023 A cache created for a branch in a workflow run can be accessed and restored from another workflow run for the same repository and branch. Multiple workflow runs in a repository can share caches. It cannot be restored by the base branch or other pull requests targeting that base branch. Because of this, the cache will have a limited scope and can only be restored by re-runs of the pull request. When a cache is created by a workflow run triggered on a pull request, the cache is created for the merge ref ( refs/pull/./merge). For example, a cache created for the tag release-a with the base main would not be accessible to a workflow run triggered for the tag release-b with the base main. Workflow runs also cannot restore caches created for different tag names. Similarly, a cache created for the feature-a branch with the base main would not be accessible to its sibling feature-c branch with the base main. For example, a cache created for the child feature-b branch would not be accessible to a workflow run triggered on the parent main branch. Workflow runs cannot restore caches created for child branches or sibling branches. For example, if the branch feature-b has the base branch feature-a, a workflow run triggered on a pull request would have access to caches created in the default main branch, the base feature-a branch, and the current feature-b branch. If a workflow run is triggered for a pull request, it can also restore caches created in the base branch, including base branches of forked repositories. Workflow runs can restore caches created in either the current branch or the default branch (usually main).
0 Comments
Read More
Leave a Reply. |