back to fetch depth 0
Fixes #ISSUE_NUMBER
undo #75783 b/c setting fetch depth 1 doesn't really help reduce time b/c most of the jobs need either master or viable/strict
also, more branches need viable/strict than i thought, so sharding isn't picking up test times (although default sharding seems to do pretty well) (regarding the jobs i didn't realize needed viable/strict: it looks like the linux-bionic jobs don't fail when `git rev-parse viable/strict` is run but viable/strict doesn't exist but the linux-xenial ones do)
pretty sure jobs are broken only b/c its using the master version of `checkout-pytorch/action.yml`
tested via #76077
Pull Request resolved: https://github.com/pytorch/pytorch/pull/76090
Approved by: https://github.com/seemethere
