chore: remove .gitkeep placeholders#5
Conversation
These were scaffolded in Phase 2 to keep empty dirs tracked. Most dirs now contain real source files; the three that don't (internal/output, tests/integration, tests/real_vm) are placeholder buckets that nothing references. Letting them disappear is cleaner than carrying empty markers. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
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: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (11)
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
1 participant
Phase 2 scaffold left .gitkeeps in 11 dirs to keep them tracked while empty. Most of those dirs now have real source files; the three that don't (
internal/output,tests/integration,tests/real_vm) are placeholder buckets nothing references. Cleaner to let them disappear.go build,go test,golangci-lint: all green locally.🤖 Generated with Claude Code