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

Move head check for a more aggressive use of cache #79

Merged

fabpot merged 1 commit into master from aggressive-cache

Mar 8, 2024

Contributor

fabpot commented Mar 8, 2024

The only downside is if the cache is unsynchronized from the target, which should not happen. If that happens, using --scratch will fix the issue.


          Move head check for a more aggressive use of cache

ca1a6ce

fabpot merged commit eaede0b into master

2 checks passed

fabpot deleted the aggressive-cache branch

March 8, 2024 07:11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment