docs: rewrite the architecture page with current descriptions and diagrams#813
Conversation
|
Warning Review limit reached
Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (6)
📒 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 |
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
* origin/main: (183 commits) chore: rename the changelog fragment to the PR number test(esmvaltool): re-mint the baselines that drifted at the current pin fix(esmvaltool): ship the ESACCI-OZONE L3-SAGE-OMPS profile file fix(esmvaltool): raise a clear error when a facet column is missing chore: rename the changelog fragment to the PR number test(pmp): re-mint the pmp baselines on linux-64 fix(pmp): derive the climatology version stamp from the diagnostic version fix(core): redact the conda platform from committed bundle provenance docs: add changelog fragment for Climate-REF#813 docs: rewrite the architecture page with current descriptions and diagrams fix(core): enable the CEDA Solr index for ESGF searches refactor(core): drop a comment that restates the change fix(core): translate an empty ESGF search into DatasetResolutionError test(core): exercise the widened compare tolerance fix(example): bump global-sst-bias test_case_version to 2 ci: harden the integration test workflow fix(core): loosen regression compare rtol to 1e-5 fix(example): accumulate global-sst-bias means in float64 fix(cli): continue test-cases fetch when a case cannot be solved chore(deps-dev): bump pip from 26.1 to 26.1.2 ... # Conflicts: # packages/climate-ref-esmvaltool/src/climate_ref_esmvaltool/dataset_registry/data.txt # packages/climate-ref-esmvaltool/src/climate_ref_esmvaltool/diagnostics/ozone.py # packages/climate-ref-esmvaltool/src/climate_ref_esmvaltool/recipe.py # packages/climate-ref-esmvaltool/src/climate_ref_esmvaltool/recipes.txt
1 participant
Description
climate-ref-coreas the dependency leaf, providers as entry-point plugins referenced only by FQN, and executors resolved from configuration.CondaDiagnosticProviderliving in core, and the ref-app ORM coupling, with Reader adoption starting in feat(backend): adopt climate_ref.results.Reader for metric values ref-app#39.Checklist
Please confirm that this pull request has done the following:
changelog/