commit
No definition
The passages, in corpus order
19 files.
MeetingTwin resources review7
- line 13
The commit and the folder never found a pair on their own: an initial import puts every file in one commit. A pair is founded by a declaration in the frontmatte…
- line 13
…er never found a pair on their own: an initial import puts every file in one commit. A pair is founded by a declaration in the frontmatter, a shared base name, …
5 other passages
- line 13
…eclaration in the frontmatter, a shared base name, a title equal to a heading, or similar extracted text; the commit and the folder proximity only reinforce it.
- 05:25
The first import of a corpus puts every file in one commit. If the commit alone grouped files, the whole repository would be one document.
- 05:25
The first import of a corpus puts every file in one commit. If the commit alone grouped files, the whole repository would be one document.
- 09:55
That is why the commit and the folder only reinforce a pair. A pair is founded by a declaration in the frontmatter, a shared base name, a title equal to a headi…
- 45:45
… panel names the signals of every scored pair: same folder, same base name, same commit, high textual overlap. And the lock file wins over the score, both ways.
TermTwin resources1
- line 6
…e tool scores their likeness (same base name, same title, similar text, same commit, or an explicit declaration) and merges them into a single page when the sco…
TermLinter1
- line 6
…e fixes with --fix, and runs the same way as an npm package, a standalone binary, a GitHub action, a GitLab component, the container image or a pre-commit hook.
TermRelease2
- line 6
… version pull request the pipeline keeps open from the changesets: the merge commit is tagged v<major>.<minor>.<patch>, every published package is packed and at…
- line 6
…ntainer has enabled each publication. Every form of a version names the same commit, so a version pinned in a pipeline, a hook or an image is one registry of ch…
APICanonical model2
- line 9
…estamp, the fingerprint of the merged profile, one entry per source with its commit, whether links across sources were resolved and the contracts imported; enti…
- line 11
…d model of the wiki with the validators the server gave, the Cypher export, and the future service. Its schema is part of what a version of the tool commits to.
DecisionNo database1
- line 8
…re. No server, no database and no state between two builds other than the pipeline cache: the model is a file that a pipeline writes, commits, diffs and serves.
Show the 12 other files
Business objectEntity1
- line 6
…ation, a domain, a locale, its declared attributes and its source with path, commit and last-modified date. Every entity has a page, rendered by the entity page…
Business objectModel1
- line 6
…d block with the tool version, timestamp, profile fingerprint and per-source commits; every entity; every link with its provenances; every finding; the term can…
Business objectBuild1
- line 6
…of the build pipeline on a configuration: the sources it ingested with their commits, the model and the build log it wrote, and its summary. The summary counts …
Business objectResource1
- line 6
…cument, a slide deck, a transcript, a contract. A resource carries its path, commit and date, and, for documents, the metadata extracted by a reader, the PDF pr…
Business objectSource1
- line 6
…fetches it into the pipeline cache without ever writing into it, records the commit of the ingestion in the build block of the model, and goes on without it whe…
ProcessBuild pipeline2
- line 12
… the checkout fetches only the files it reads; record for each file the last commit that touched it and its date, from the repository holding a local folder too…
- line 12
…; record for each file the last commit that touched it and its date, from the repository holding a local folder too when the file is unchanged since its commit.
ProcessOnboarding a repository1
- line 16
Publish: commit the configuration repository, add the pipeline of the forge that builds on every push and every morning and publishes dist/ on GitHub Pages or G…
ProcessPublishing the wiki1
- line 16
The site is uploaded as the Pages artifact and deployed; the published site names the commit of every source in the build block of its model.
ProcessRelease3
- line 7
…tLab component at the same version. Every form of one version names the same commit: the tag, the packages on npm, the image, the action, the component and the …
- line 7
…e tag, the packages on npm, the image, the action, the component and the pre-commit hook. Versions follow semantic versioning; before 1.0.0 a minor version may …
1 other passage
- line 14
The release workflow tags the merge commit v<x.y.z>, builds the standalone binaries on three platforms, packs every published package, verifies the licence inve…
ScreenAbout this wiki1
- line 15
…gives one, else the labels of the dominant types of the space), VERSION (the commit the build read, shortened to seven characters, empty for a local source with…
ScreenMeeting page1
- line 20
…pairs the reconciliation scored, "3 files: same folder, same base name, same commit, high textual overlap.", absent when the model recorded none. The related pa…
ScreenContract viewer1
- line 12
…t changed relative to the build, "imported 9 days ago": the date of the last commit of the file in its repository, the file date outside one, and the instant of…
What we know
- Occurrences
- 29
- Files
- 19
- Spaces
- Briefs, Glossary, Specifications
No declared property: there is no file for this word.
See the neighbourhood map6 pages6Neighbourhood mapcommit
Neighbourhood map commit
Distance1 hop
50 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.