Summary:
This was discovered during https://github.com/pytorch/pytorch/issues/63408. For some reason only this checkout action is not correctly set fetch-depth
Pull Request resolved: https://github.com/pytorch/pytorch/pull/63770
Reviewed By: malfet, janeyx99
Differential Revision:
D30486110
Pulled By: walterddr
fbshipit-source-id:
a67395cca2487407ed0d49c8c89587935ca5f212
- name: Checkout PyTorch
uses: actions/checkout@v2
with:
+ fetch-depth: 0 # deep clone, to allow sharding to use git rev-list
submodules: recursive
- name: Pull docker image
run: |
- name: Checkout PyTorch
uses: actions/checkout@v2
with:
+ fetch-depth: 0 # deep clone, to allow sharding to use git rev-list
submodules: recursive
- name: Pull docker image
run: |
- name: Checkout PyTorch
uses: actions/checkout@v2
with:
+ fetch-depth: 0 # deep clone, to allow sharding to use git rev-list
submodules: recursive
- name: Pull docker image
run: |
- name: Checkout PyTorch
uses: actions/checkout@v2
with:
+ fetch-depth: 0 # deep clone, to allow sharding to use git rev-list
submodules: recursive
- name: Pull docker image
run: |
- name: Checkout PyTorch
uses: actions/checkout@v2
with:
+ fetch-depth: 0 # deep clone, to allow sharding to use git rev-list
submodules: recursive
- name: Pull docker image
run: |
- name: Checkout PyTorch
uses: actions/checkout@v2
with:
+ fetch-depth: 0 # deep clone, to allow sharding to use git rev-list
submodules: recursive
- name: Pull docker image
run: |
- name: Checkout PyTorch
uses: actions/checkout@v2
with:
+ fetch-depth: 0 # deep clone, to allow sharding to use git rev-list
submodules: recursive
- name: Pull docker image
run: |