@sppatel is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

Appreciate the quick feed back - will address the review comments.

Ok - I think I addressed the current set of review comments. One thing I realized was that this "may" require remote cache implementations to support HEAD requests to take advantage of this feature.

@gsoltis I also locally implemented HEAD support for https://github.com/ducktors/turborepo-remote-cache - in order to verify functionality.

@sppatel I think the linter issue is real, the other test failure looks unrelated.

How can I rerun to verify the lint fixes?

Locally i also received this error on the naming of CacheState

exported: type name will be used as cache.CacheState by other packages, and that stutters; consider calling this State (revive)go-golangci-lint

I went with the recommended name of "State" - but if you'd want something different/more explicit - happy to change it.

make lint-go will run the linter locally. You might need to brew install golangci-lint if you don't have it already.

re: State, maybe ItemStatus or something like that? We're going to have a CacheItem soon, so I think ItemStatus will make sense in context: https://github.com/vercel/turborepo/pull/1991/files#diff-b0746dbe930e7be5e528cdaf2505200affe533e60e22316a1f03616f4e68f2c3

Mind re-kicking the status checks again when u get a moment to see if we're good now?

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Test failure is unrelated. Force-merging.

@sppatel I know this is something people have been asking for, thanks for diving in on it!

Absolutely! Appreciate all the help and feedback!