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.

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

Jump to bottom

Documentation update for cache #873

Merged
merged 5 commits into from
Jul 10, 2024
Merged

Documentation update for cache #873

Changes from 4 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
6a48d6d
updated doc
May 22, 2024
17f3180
added note
Jun 4, 2024
2d8df3f
modify1
Jun 6, 2024
4e6b3db
Update advanced-usage.md
gowridurgad Jul 9, 2024
2506039
Update 0000-caching-dependencies.md
gowridurgad Jul 10, 2024
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
4 changes: 3 additions & 1 deletion docs/adrs/0000-caching-dependencies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,9 @@ Integration of caching functionality into `actions/setup-python` action will bri

We will add support for Pip and Pipenv dependency caching.

We won't pursue the goal to provide wide customization of caching in the scope of `actions/setup-python` action. The purpose of this integration is to cover ~90% of basic use-cases. If users need flexible customization, we will advise them to use `actions/cache` directly.
We won't pursue the goal to provide wide customization of caching in the scope of `actions/setup-python` action. The purpose of this integration is to cover ~90% of basic use-cases.

The actions/setup-python action does not provide customization of caching based on specific dependencies installed within each job. If different dependencies are installed across jobs the cache from the first job will be used in the second job. To manage this aspect, users should create separate caches for jobs with different requirements. If users need flexible customization, we will advise them to use `actions/cache` directly.

## Decision

Expand Down