Tessri on itself
The latest change on Tessri's own main is pull request #29, “The front doors do more: the site searches the guide, pages know their neighbours and their card, and the repository explains itself”, merged as fbb6833c5. Below is the page tessri brief --since 12e6c2cd6 hands a person for it: the change compared with main as it was before it (12e6c2cd6), built when the site was deployed, and every push to main rebuilds it. The HTML report of the repository, with the module graph and the impact explorer, is what tessri scan . --format html writes, built the same way.
Review brief: tessri
12e6c2cd6 (base 12e6c2cd6) to HEAD fbb6833c5. 4 code files changed (0 added, 4 modified, 0 deleted), 429 lines; 10 other files (249 lines of config, docs and the like).
1 commit on the way, by Tianyi Zhang, in their words:
d18fd37e2The front doors do more: the site searches the guide, pages know their neighbours and their card, and the repository explains itself (Tianyi Zhang)
Look first
| # | File | Why | This change | Owners | Flags |
|---|---|---|---|---|---|
| 1 | tools/build_site.py | 15 commits in 90 days | +251 -12 | Tianyi Zhang 100% | - |
| 2 | site/index.html | 15 commits in 90 days | +5 -5 | Tianyi Zhang 100% | - |
| 3 | site/tessri.css | 9 commits in 90 days | +83 -1 | Tianyi Zhang 100% | - |
| 4 | tests/test_site.py | 6 commits in 90 days | +71 -1 | Tianyi Zhang 100% | test file |
Nobody other than the authors maintains the changed files, as far as history shows.
What it did to the structure
No structural findings: the change adds no orphan, cycle, dangling import or unowned code that this analysis can see.
Nothing outside the change imports it, as far as static imports show.
Not analysed: site/tessri.css (CSS, no analyzer), so dependents, candidate tests and structure are unknown for it.
Not analysed: site/index.html (HTML, no analyzer), so dependents, candidate tests and structure are unknown for it.
Validation
Candidate tests, nearest first: tests/test_site.py. They reach the changed files; they are paths, not results.
Checks the host ran: none recorded. Record each with --ran "<command>: <result, exit code>", or hand over a test report with --report or a coverage report with --coverage.
Open for a person
- Only the author maintains
site/index.html,site/tessri.css,tests/test_site.py,tools/build_site.py: a second reader has to come from outside the file's history. site/tessri.css: no analyzer covers CSS, so dependents, candidate tests and structure are unknown for this file.site/index.html: no analyzer covers HTML, so dependents, candidate tests and structure are unknown for this file.- No check was recorded as run: the candidate tests are paths, not results.
Read this with care
- This page selects from
tessri triageandtessri check, run from one analysis of the base and one of the working tree; the JSON carries both objects whole, so a list shortened here hides nothing there. - Files are ordered by how many commits touched them in the last 90 days, then by how much this change touches; in a backtest on one repository that predicted later fixes better than the size of the change alone. It says where trouble tends to be, not that this change is wrong, and a new file has no history, so it sorts by its size.
- Dependents, candidate tests and findings rest on what the analyzers see between files of this repository, static imports above all; a name in a string or a dynamic import is a guess, and the one finding that rests on it,
dangling-reference, says so. Runtime wiring, registries and consumers outside the repository are invisible, and no finding is proof that the rest is fine. - History is read up to the base, so the change's own commits do not count as activity and its authors do not count as owners. The commit subjects are the authors' words; the intent behind a change is not inferred from the files it touches.
- Candidate tests are paths that reach the change, never executions; only what
--ranrecords, or a test or coverage report the host wrote and--reportor--coveragereads, was run. A coverage report says which statements ran, not what any test asserted about them, and its line numbers are those of the files when the host ran the tests.
Built from this checkout by tools/build_site.py with --demo; the brief guide explains every section, and the report guide the explorer.