Skip to content

Change branches to branches/tags #20048

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.

Sign up for GitHub

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

Merged
hubwriter merged 5 commits into from
Aug 30, 2022
Merged

Change branches to branches/tags #20048

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
a42ca48
Update caching-dependencies-to-speed-up-workflows.md
Phantsure Aug 22, 2022
d84342f
Add more explanation
Phantsure Aug 22, 2022
5f6ae70
Update content/actions/using-workflows/caching-dependencies-to-speed-…
hubwriter Aug 30, 2022
ff1e0d2
Merge branch 'main' into patch-2
hubwriter Aug 30, 2022
4db04f6
Merge branch 'main' into patch-2
hubwriter Aug 30, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ For more information on workflow run artifacts, see "[Persisting workflow data u

A workflow can access and restore a cache created in the current branch, the base branch (including base branches of forked repositories), or the default branch (usually `main`). For example, a cache created on the default branch would be accessible from any pull request. Also, if the branch `feature-b` has the base branch `feature-a`, a workflow triggered on `feature-b` would have access to caches created in the default branch (`main`), `feature-a`, and `feature-b`.

Access restrictions provide cache isolation and security by creating a logical boundary between different branches. For example, a cache created for the branch `feature-a` (with the base `main`) would not be accessible to a pull request for the branch `feature-c` (with the base `main`).
Access restrictions provide cache isolation and security by creating a logical boundary between different branches or tags. For example, a cache created for the branch `feature-a` (with the base `main`) would not be accessible to a pull request for the branch `feature-c` (with the base `main`). On similar lines, a cache created for the tag `release-a` (from the base `main`) would not be accessible to a workflow triggered for the tag `release-b` (with the base `main`).

Multiple workflows within a repository share cache entries. A cache created for a branch within a workflow can be accessed and restored from another workflow for the same repository and branch.

Expand Down