prodockit 0.40.0
-
Added:
prodockit template-sync --pushfinishes a sync where the
pipeline can see it (#502).--applystops at staged, on its own branch, and that publishes
nothing: both hosts build only from the default branch, so a sync
sitting on atemplate-update-...branch produces no pipeline and no
rebuilt site even after you commit and push it.--pushcommits,
merges into the branch your host builds from, and pushes - showing
what it will do and waiting for a yes first.It assumes you merge your own work, with no merge request in the way.
A project that gates its default branch should use--applyalone and
raise a merge request from the update branch. -
Fixed: a stale checkout beside a project no longer stops
template-sync(#500).A checkout beside the project wins over fetching, which is right for
somebody editing the template and their project together - but it won
unconditionally, so an old clone taken before the template carried a
manifest stopped the command outright, with a usable copy one fetch
away. A sibling now has to carry a manifest to be preferred, and the
run says which checkout it passed over. -
Fixed: the installation page lists every extension (#504).
It explained how to enable an extension and then named four of the
nine.prodockit.tables,.tree,.steps,.bibliographyand
.indexhad each arrived with an entry point and a documentation page
without reaching the one page a new reader goes to first. A test now
treats the entry points as the authority, so a registered extension
cannot go undocumented again. -
Changed: the
template-syncmanual covers a finished sync, not just
--apply(#503).What to do with a
.newsidecar and how to tell "you edited this"
from "you never received this update"; that--forcetakes exact
paths one flag at a time; that a second run branches again; and that
committing alone changes nothing on the host. -
Added:
\ref{id}resolves a captioned figure or table, not only a
heading (#506).A reference to a figure renders its label - Figure 3.1 - linked to
the figure, and updates itself when figures are added or moved. Until
now the number had to be typed by hand beside a\refthat could not
resolve it, so a document said "Figure 3.1" in prose while the figure
itself was numbered by the stylesheet, with nothing keeping the two in
step.Figures and tables count separately, and both take the page's chapter
number - the same numbering the caption shows, so a reference and its
target always agree. Numbered in the same pass that numbers headings,
which is where the chapter number already exists.A caption reference is its label alone, where a heading reference
keeps its name: "the components in Figure 3.1" reads badly as "Figure
3.1 Component Model", while a bare "1.1" says nothing about where a
reader is being sent.