Skip to content

Commit 6fb366f

Browse files
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

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

.github/workflows/main.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,8 @@ jobs:
2424

2525
steps:
2626
- uses: actions/checkout@v4
27+
with:
28+
fetch-depth: 0
2729

2830
- uses: mlugg/[email protected]
2931
with:

0 commit comments

Comments
 (0)