fix: Uninstall CLI no longer reinstalls the global command#1126
Conversation
Stop the editor startup path from reinstalling the package-owned global CLI after a user chooses Uninstall CLI. Keep CLI installation as an explicit Settings action and remove the now-unused ensure-current workflow.
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (5)
✨ 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 |
Keep the new startup guard test aligned with the repository rule that every test method states the behavior it verifies.
Summary
uloopcommand removed instead of reinstalling it during editor startup.User Impact
Changes
Verification
go run ./cmd/uloop run-tests --project-path /Users/a12115/ghq/hatayama/unity-cli-loop2 --test-mode EditMode --filter-type regex --filter-value "InfrastructureEditorStartup_WhenLoaded_DoesNotScheduleGlobalCliAutoInstall|CliSetupApplicationServiceTests"go run ./cmd/uloop compile --project-path /Users/a12115/ghq/hatayama/unity-cli-loop2git diff --checkCloses #1123