Repository navigation
ci(growth): take main's growth since the #93 seed into the baseline - #184
Merged
Merged
Conversation
napetrov
requested review from
antonwolfy,
jharlow-intel,
vchamarthi and
xaleryb
as code owners
October 22, 2026 19:49
napetrov
added
the
skip-changelog
intel#93 merged with a baseline seeded before intel#120, intel#165, intel#171 and intel#180 landed, so the ratchet test fails on main and on every open PR: llm.py, four functions grew past or over the cap, and novelty/bundle.py shrank under it. Raise those entries with a rationale and drop the bundle.py entry. Signed-off-by: Nikolay Petrov <nikolay.a.petrov@intel.com>
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #184 +/- ##
==========================================
+ Coverage 91.64% 91.65% +0.01%
==========================================
Files 222 222
Lines 27409 27409
Branches 4508 4508
==========================================
+ Hits 25118 25122 +4
+ Misses 1620 1617 -3
+ Partials 671 670 -1 🚀 New features to boost your workflow:
|
vchamarthi
approved these changes
Oct 22, 2026
vchamarthi
left a comment
vchamarthi
left a comment
Contributor
There was a problem hiding this comment.
The baseline now matches main and the ratchet test passes at this head; no blocking issues.
napetrov
pushed a commit
to antonwolfy/dokimi
that referenced
this pull request
Oct 22, 2026
…e in intel#153 intel#184 already took main's growth since the intel#93 seed into the baseline with a generic rationale. Name the PR behind each of those entries instead, and add dokimi/repos/compare.py::_provenance_warnings, which intel#153 took over the complexity cap after intel#184 and which turns main's Tests job red again.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mainis red since #93 merged:tests/test_growth_ratchet.pyfails on main and on every open PR'sTests (py3.x)job. #93's baseline was seeded before #120, #165, #171 and #180 landed, so their growth reads as new violations.dokimi/llm.pylinesJudge._judge_answerJudgePanel._call_judgemanifest.py::_check_taskrepo_run.py::_contextnovelty/bundle.pylines--update)Baseline only; no code change.
Evidence
python scripts/check_growth.pyonintel/main40ae743: 6 violations. With this commit: 0.pytest tests/test_growth_ratchet.py: 45 passed, 1 skipped.Merge Danger
Low. Open PRs that touched these files will need a
--updateor a re-raise after merging main. Splitting the grown functions is left to their own PRs, as the rationale says.🤖 Generated with Claude Code