Report elapsed time in the success message - #136
Conversation
|
Warning Review limit reached
Next review available in: 3 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe archive command now measures archive-generation time and includes minutes and seconds in successful ZIP and tarball messages. Feature scenarios in ChangesArchive elapsed-time output
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 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. 📢 Thoughts on this report? Let us know! |
|
@coderabbitai review |
✅ Action performedReview finished.
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/Dist_Archive_Command.php`:
- Around line 184-188: Update the project’s Composer/PHPCS configuration so the
WP_CLI and WordPress coding-standard sniffs used by composer test are installed
and discoverable. Ensure composer test completes successfully without
missing-sniff errors, while preserving the existing validation commands.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: a44ee168-0cce-4fd7-b00e-0028a015ec55
📒 Files selected for processing (3)
features/dist-archive.featurefeatures/distignore.featuresrc/Dist_Archive_Command.php
Edit: I found it very helpful to see the time taken when working on #134 / #135:
This PR is a pretty simple end - start
time()in__invoke().Claude:
Implements the profiling suggestion from #134 ("Provide additional context/Screenshots"), as a follow-up to #135.
The success message now includes how long archive generation took, so slow runs (like the 8m32s in #134) are visible:
Dist_Archive_Command::__invoke()records the start time and appendsin {minutes}m {seconds}s.to the success output, using the exact code suggested in the issue.STDOUT should matchregexes in the Behat features are updated to expect the new suffix; theSTDOUT should containassertions are unaffected.Ref #134
🤖 Generated with Claude Code
Summary by CodeRabbit