There's so much accidental complexity in the CI workflow purely to enable a tiny amount of caching. I hope the next generation of CI tools can improve this situation.
I know. I've been wondering if there's a way this complexity could be buried in the GitHub action for dprint (https://github.com/dprint/check) so people would only have to specify that and everything would just happen, but I'm not sure it's possible at the moment. Caching seems to be limited to needing to use actions/cache (https://github.com/actions/cache)