Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.
Page 124 of 221; 24 results per page.
Someone committed a file that still contained conflict markers, and merging that commit produced markers inside markers. Region matchers that pair the first `<<<<<<<` with the first `=======` split this file in the wrong place and produce two overlapping regions that cannot both be resolved.
Documentation about merge conflicts that quotes the markers inside a fenced code block, and then genuinely conflicts further down. A pre-commit hook that greps for `^<<<<<<<` reports two hits and blocks a clean commit; one that understands Markdown fences reports the one that matters.
One file left with three independent unresolved regions and clean text between them, which is what a real deployment-values merge looks like. Editors that jump to 'the next conflict' and resolvers that report a boolean rather than a count both get exercised here.
A working-tree file left mid-merge in git's default `merge` conflict style: our version, a row of equals signs, their version, and branch labels on the opening and closing markers. Both sides happen to end with the same line, which the zdiff3 twin in this group hoists out and this style repeats.
The identical merge under `merge.conflictStyle=zdiff3`, which hoists lines common to both sides out of the conflict region; here 'jitter: on' moves below the closing marker. Diff this against the diff3 twin to see that the same conflict produces different file contents depending on one config value.
The message template git writes into .git/MERGE_MSG when a merge stops on conflicts: one real subject line followed by a commented list of the conflicted paths and the standard advice block. Everything after the first blank line is stripped by `git commit`, so a hook that lints the whole file rejects messages git would accept.
A Mermaid stateDiagram-v2 describing environment promotion with canary and rollback transitions, start and end pseudostates, and a note block. A second Mermaid diagram type, so a renderer is not only tested on flowcharts.
A Mermaid flowchart of an order-fulfilment process as diagrams-as-code, for testing Mermaid rendering, diagram-to-image conversion, and Markdown pipelines that embed Mermaid.
The shared six-task ETL topology as a Mermaid flowchart, with mixed node shapes, a subgraph, a classDef and %% comments. The Mermaid twin of the Graphviz fixture, for scoring diagram-format converters against one known answer.
High-resolution cylinder mesh: the ground truth for scoring a decimation / simplification tool against the low-poly member of this group.
High-resolution sphere mesh: the ground truth for scoring a decimation / simplification tool against the low-poly member of this group.
High-resolution torus mesh: the ground truth for scoring a decimation / simplification tool against the low-poly member of this group.
High-resolution vase mesh: the ground truth for scoring a decimation / simplification tool against the low-poly member of this group.
Low-poly simplification of the same cylinder shape (36 triangles vs 192). Compare against the dense ground truth to measure decimation error.
Low-poly simplification of the same sphere shape (140 triangles vs 1728). Compare against the dense ground truth to measure decimation error.
Low-poly simplification of the same torus shape (196 triangles vs 1600). Compare against the dense ground truth to measure decimation error.
Low-poly simplification of the same vase shape (100 triangles vs 480). Compare against the dense ground truth to measure decimation error.
Ground-truth mesh cut-out with transparent holes.
Chain-link / mesh with interior holes. Tests whether a removers keeps background visible through the grid.
Binary mask for the mesh-fence hard case.
Watertight box mesh: the intended result for a mesh-repair / hole-filling tool applied to the broken member of this group.
Watertight sphere mesh: the intended result for a mesh-repair / hole-filling tool applied to the broken member of this group.
Watertight tube mesh: the intended result for a mesh-repair / hole-filling tool applied to the broken member of this group.
Deliberately broken box mesh (missing top face). Feed to a mesh-repair tool and compare the result against the watertight ground truth.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.
