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
With this modification and caching enabled, cargo vcpkg build seems to build with the new branch but on the old remote. I think the cache should be invalidated when either of them change.
From https://github.com/microsoft/vcpkg
fa1bbe097..261c458af master -> origin/master
Checkout rev sdl-hidapi
error: pathspec 'sdl-hidapi' did not match any file(s) known to git
The text was updated successfully, but these errors were encountered:
@kornelski is right in that branch must be used instead of rev if you intend to track a branch instead of pinning to a specific commit revision.
If "caching enabled" here refers to using actions/cache@v2 then I don't think there is a good way to generate the key for the cache such that the key gets updated when the branch being tracked moves, as the file the key is based off of (Cargo.toml in this case) isn't touched when the branch changes.
With this modification and caching enabled,
cargo vcpkg build
seems to build with the new branch but on the old remote. I think the cache should be invalidated when either of them change.The text was updated successfully, but these errors were encountered: