docs: publish-cycle says what a WARN or ERROR from the page export after publish means, architecture names the page export as the way out for a reader that cannot ask (#214 close); 10.0.0-beta.14
Files changed: - CHANGES.md - VERSION - docs/explanation/architecture.md - instructions/publish-cycle.md Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2
This commit is contained in:
1 parent
99945c4841
commit
d92800f372
4 files changed
+16
-2
No files matched your search
@@ -58,6 +58,13 @@ consistent.
|
||||
writable, say. Do **not** run `publish` again: it would have nothing to push and back nothing up.
|
||||
Once the user has fixed the cause, `tools/wikitool backup run` repeats the backup
|
||||
([docs/how-to/back-up-to-a-synced-folder.md](../docs/how-to/back-up-to-a-synced-folder.md)).
|
||||
- **A `WARN` that a page export failed?** The same: the commit and the push stand, `publish`
|
||||
exited 0, and the line names the target and the reason - a page someone edited in the target
|
||||
folder, say. Show it to the user and do **not** run `publish` again; once the cause is fixed,
|
||||
`tools/wikitool export run` refreshes the target
|
||||
([docs/how-to/export-to-a-synced-folder.md](../docs/how-to/export-to-a-synced-folder.md)).
|
||||
An `ERROR` about the `export` section instead stopped `publish` before it committed: the section
|
||||
is the user's to fix by hand, and nothing was published.
|
||||
- **Query or lint pass?** Neither auto-publishes. Run `publish` only if asked to.
|
||||
- **Nothing under `kb/` changed?** Skip steps 1 and 2; a change to `tools/` or `instructions/`
|
||||
does not affect the catalog.
|
||||
|
||||
Reference in new issue
Block a user