Repository navigation
chore: quiet lint gate output - #49
Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ 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: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (8)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Review rate limit: 0/5 reviews remaining, refill in 7 minutes and 13 seconds. Comment |
8a4cd36 to
fd21e00
Compare
2ace614 to
0425315
Compare
0425315 to
ea72cc0
Compare
ea72cc0 to
a5252e9
Compare
9cd3bf9 to
65dd9ca
Compare
65dd9ca to
6643fa8
Compare
a5252e9 to
b99eaa9
Compare
Merge activity
|

Quiet lint gate output by scoping lint inputs and fixing lint warnings
lintscript in package.json tosrc,tests,config,package.json, andtsconfig.jsoninstead of the entire repo, reducing noise.Array.findIndexwithArray.indexOffor locating'--out'across several e2e fixture files.?? 0) in tests/helpers/image.ts, preventing NaN propagation indiffRgbwhen channel values are undefined.parseJsonStdoutto simplify the last-line check.Macroscope summarized b99eaa9.