You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any reason why shake would report ALL source files as changed if the .shake.database file (along with the source files) are moved between cloud servers?
What about doing a git checkout $CI_COMMIT_SHA on the source dir?
PS: Using shakeChange=ChangeDigest
The text was updated successfully, but these errors were encountered:
If you use --trace the trace log should say why the files are considered different. As long as their path and SHA1 are the same, I wouldn't have thought anything would be considered to have changed.
Is there any reason why shake would report ALL source files as changed if the
.shake.database
file (along with the source files) are moved between cloud servers?What about doing a
git checkout $CI_COMMIT_SHA
on the source dir?PS: Using
shakeChange=ChangeDigest
The text was updated successfully, but these errors were encountered: