[Docs] Read from the snapshots branch, trim the headings and the comments - #40
Merged
Merged
Conversation
The nightly publishes by replacing everything in the branch it writes, so the first run deleted TileOPs-nightly's own README and licence. It now writes a `snapshots` branch instead, and main is left to the repository itself. Same three files, one commit per run, a different branch to read them from.
lcy-seso
force-pushed
the
feat/nightly-data-branch
branch
from
August 30, 2026 04:16
81a08e7 to
a1cedd3
Compare
lcy-seso
changed the title
The heading carried `(3 workloads · ✅)`, and the heading is what the page's table of contents shows: 189 entries, half of them ending in a tick that says every op passed, which is what a reader assumes anyway. The workload count is the length of the list immediately under it. What survives is the mark that warns — ❌ where the correctness run failed, ⏭️ where it was skipped. On the last snapshot that is no op at all; when it is one, it is the only one wearing anything.
lcy-seso
force-pushed
the
feat/nightly-data-branch
branch
from
August 30, 2026 04:49
bc8a143 to
0441ab9
Compare
lcy-seso
added a commit
to tile-ai/TileOPs
that referenced
this pull request
Aug 30, 2026
…2009) Follows #2008. Pairs with tile-ai/TileOPs.github.io#40; either order is safe. ## Problem The publish replaces everything in the branch it writes. Pointed at `main`, the first run deleted TileOPs-nightly's README and licence — those belong to whoever maintains that repository, not to this job. ## Change The snapshot goes to a `snapshots` branch of its own: one commit per run, three files, and everything not in the payload deleted there — which is what keeps a stale `test_results.xml` from passing for tonight's. `main` holds what the repository says about itself, and nothing publishes over it.
The comments in this repository argue with themselves: nearly every one states a decision, then restates it as the case against the alternative, then names the symptom that alternative produced. Three sentences where the decision plus one clause is the whole content — and a comment nobody finishes reading is a comment nobody maintains. Compressed, not deleted. Every comment kept was tested against one question: would removing it let someone undo the decision by accident? The palette's cast, `color-mix()` being dropped whole by engines that cannot parse it, the middot that separates without claiming to align, the package deciding an op's family before the keyword list — those stay, because each is a rule somebody would otherwise reverse. `workload_shape`'s module docstring also stops describing a merge that does not happen: templates are read only where no shape is given outright, all or nothing, which is what the code has always done. 847 comment lines to 722, the stylesheet from 421 to 340.
lcy-seso
changed the title
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
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.
Pairs with tile-ai/TileOPs#2009. Either order is safe: the
snapshotsbranch already holds the snapshot from run 33289823876.Read from the snapshots branch
The nightly publishes by replacing everything in the branch it writes. Pointed at
main, the first run deleted TileOPs-nightly's README and licence — those belong to whoever maintains that repository. It now writes asnapshotsbranch, and this reads from there: same three files, one commit per run.An op's heading is its name
The heading carried
(3 workloads · ✅), and the heading is what the page's table of contents shows — 189 entries, 88 of them ending in a tick that says the op passed, which is what a reader assumes anyway. The workload count is the length of the list immediately under it.What survives is the mark that warns: ❌ where the correctness run failed, ⏭️ where it was skipped. On the last snapshot that is no op at all. The golden pages carry the change, and the fixture covers all three cases.
Say each design decision once
The comments here argue with themselves: nearly every one states a decision, restates it as the case against the alternative, then names the symptom that alternative produced. Compressed, not deleted — every comment kept was tested against one question: would removing it let someone undo the decision by accident?
workload_shape's module docstring also stops describing a merge that does not happen: templates are read only where no shape is given outright, all or nothing, which is what the code has always done.847 comment lines to 722; the stylesheet from 421 to 340.
Checks
pytest,ruff,stylelint,mkdocs buildpass. Rendered against the live branch: 189 ops, 1139 workloads.