Repository navigation
docs: sync TESTING.md and README with current test matrix - #457
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 10 minutes and 33 seconds. ⌛ 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: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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 |
|
When a commit only touches docs, tests, or CI config, docker-publish.yml does not trigger (it path-filters on packages/**, Dockerfile*, etc). The deploy was hard-aborting after 60s waiting for a run that will never appear, causing every docs/test/chore commit to fail deployment. Fix: when no docker-publish run is found and the commit did not touch any Docker-relevant paths, skip the image wait and proceed with the existing latest images. The ::notice annotation makes the skip visible in the run log. Also improves the error message when a docker-publish run IS expected but missing — now lists which changed files triggered the expectation. Fixes deploy failures on: docs/testing-release-metadata-sync (#457), chore/shared-test-lane (#460), and similar non-image commits.
* ci(deploy): skip docker-publish wait for non-image commits When a commit only touches docs, tests, or CI config, docker-publish.yml does not trigger (it path-filters on packages/**, Dockerfile*, etc). The deploy was hard-aborting after 60s waiting for a run that will never appear, causing every docs/test/chore commit to fail deployment. Fix: when no docker-publish run is found and the commit did not touch any Docker-relevant paths, skip the image wait and proceed with the existing latest images. The ::notice annotation makes the skip visible in the run log. Also improves the error message when a docker-publish run IS expected but missing — now lists which changed files triggered the expectation. Fixes deploy failures on: docs/testing-release-metadata-sync (#457), chore/shared-test-lane (#460), and similar non-image commits. * ci(deploy): address review — consolidate path pattern, detect gh api failure
* ci(deploy): skip docker-publish wait for non-image commits When a commit only touches docs, tests, or CI config, docker-publish.yml does not trigger (it path-filters on packages/**, Dockerfile*, etc). The deploy was hard-aborting after 60s waiting for a run that will never appear, causing every docs/test/chore commit to fail deployment. Fix: when no docker-publish run is found and the commit did not touch any Docker-relevant paths, skip the image wait and proceed with the existing latest images. The ::notice annotation makes the skip visible in the run log. Also improves the error message when a docker-publish run IS expected but missing — now lists which changed files triggered the expectation. Fixes deploy failures on: docs/testing-release-metadata-sync (#457), chore/shared-test-lane (#460), and similar non-image commits. * ci(deploy): address review — consolidate path pattern, detect gh api failure
This branch was successfully deployed
1 participant
Summary
Why
The testing documentation drifted significantly from reality. The frontend now has 451 Vitest unit tests, the bot has 1373 Jest tests, and the backend has 672 — none of which were reflected in the docs.
Checklist