Fix CI traceability job: use full clone#31
Conversation
actions/checkout@v4 defaults to fetch-depth: 1 (shallow clone). When git-warp materializes, it walks commit parent chains via git show to read patch blobs. In a shallow clone, these commit objects may not exist locally, causing 'git show' to fail with exit code 128. Setting fetch-depth: 0 ensures the full object database is available before fetching WARP writer refs.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoRun configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe CI workflow configuration is updated to enable full repository history fetching during checkout and adds a new setup step that configures git identity credentials (user.name and user.email) for graph materialization operations within the traceability job. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
git-warp's auto-checkpoint calls git commit-tree during materialization, which requires a committer identity. CI runners have no git user configured, causing exit code 128 (fatal: empty ident name). Sets a local git identity in the traceability job only.
Summary
Git command failed with code 128becauseactions/checkout@v4defaults tofetch-depth: 1(shallow clone)git show— in a shallow clone, patch commit objects aren't present locallyfetch-depth: 0on the checkout step so the full object database is available before fetching WARP writer refsRoot cause
Test plan
Summary by CodeRabbit