Allow commits with /nocache
to not use the cache
#2909
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
Pull request overview
/nocache
, then it will not use the existing cache.Details
From now on, a commit message containing
/nocache
will cause a CI run without the existing cache. Note that this does not refresh the cache, it just ignores the cache for that commit only. On thedevelop
branch, it is recommended (for admins) to go toSecrets > CACHE_VERSION
and change the value, after which you can go to Actions and "Restart this workflow". No new commit required here.However, this does not work on PRs. That's what this PR is for. If any PR in the future is failing because of cache issues (which would only be if
nltk_data
was updated very recently), then an empty commit can be pushed withgit commit --allow-empty -m "Restarting CI without cache: /nocache"
. This should cause a CI run without a cache.