Cache doesn't work when the project is not in the root of the repository.
See original GitHub issueDescription:
Add an input to the action (working-directory
or project-directory
) to specify the path to the project, where the pyproject.toml
file is located. Use this directory to look for the pyproject.toml
and cached deps.
Justification: Caching doesn’t work for projects where the project is not in the root of the repository.
Issue Analytics
- State:
- Created a year ago
- Reactions:19
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Cannot create cache directory .. or directory is not writable ...
composer folder was created by the root. Run this to fix the issue: $ sudo chown -R $USER $HOME/.composer.
Read more >Failed to synchronize cache for repos for RHEL 8
When I run dnf repolist on rhel 8 enabled machine I see the following error "Failed to synchronize cache for repo" as seen...
Read more >Caching in GitLab CI/CD
A cache is one or more files a job downloads and saves. Subsequent jobs that use the same cache don't have to download...
Read more >TortoiseSVN's Settings
Items deleted from the repository, missing from the working copy, ... Disadvantage: Since only one folder is cached, the overlays don't show the...
Read more >Invalidate caches | IntelliJ IDEA Documentation - JetBrains
The caches will not be deleted until you restart IntelliJ IDEA. · Opening and closing a project without invalidating the cache does not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi, @atayardimci 👋 Thank you for the feature request, we will take a look at it and get back to you with updates.
I’ve been workarounding it as follows for now
I hope this feature request be integrated into setup-python : )