Commit 6fb366f
committed
Use full clone in GitHub Actions
Configure actions/checkout to fetch the entire repository history instead of a shallow clone. This fixes the "shallow update not allowed" error when creating the repository database during releases.
The repo-db build step needs to push the entire repository to a temporary bare repo, which requires full history.
## Test plan
The error only occurs in CI with shallow clones. With fetch-depth: 0, the workflow will clone the full repository and the git push --mirror command will succeed.1 parent f52faf2 commit 6fb366f
1 file changed
+2
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
24 | 24 | | |
25 | 25 | | |
26 | 26 | | |
| 27 | + | |
| 28 | + | |
27 | 29 | | |
28 | 30 | | |
29 | 31 | | |
| |||
0 commit comments