Repository navigation
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe GitHub Pages repository flow now performs a shallow, single-branch clone at ChangesGitHub Pages branch cloning
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This localized change updates branch checkout behavior, and no actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #364 +/- ##
==========================================
+ Coverage 89.24% 89.88% +0.63%
==========================================
Files 16 16
Lines 958 949 -9
Branches 203 203
==========================================
- Hits 855 853 -2
+ Misses 103 93 -10
- Partials 0 3 +3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
### Description Follow-up to #364, addressing review findings: - Add a gh-repository retry test covering push rejected → reset --hard HEAD~1 → rmRF → shallow re-clone - Add a clone() argv unit test in test/git.spec.ts - Extract otherRepoGitHistory() helper to dedupe the other-repository test expectations - Comment the shallow/single-branch clone rationale in src/write.ts - README: note that with gh-repository the action shallow-clones the target branch directly ### Test scenario - [ ] CI green (jest, lint, build) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Documentation** - Clarified that specifying a GitHub Pages repository uses a shallow clone of only the `gh-pages` branch. - Added details explaining repository cloning behavior when publishing benchmarks. - **Bug Fixes** - Ensured an `index.html` file is created when needed without overwriting an existing file. - **Tests** - Expanded coverage for authenticated repository cloning and branch-specific operations. - Added coverage for push rejection scenarios and safer rollback handling. - Added coverage for `index.html` creation and preservation behavior. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
|
released in v1.22.2 |
This PR modifies the action to shallow clone the target branch only.
Why: For large repos, the time to do a full clone and checkout can be 20 minutes plus, which is long enough to cause retry loops when the branch tip is under contention by multiple benchmark runs.
Summary by CodeRabbit