novoyuuparosk-wiki/novoyuuparosk-auto-wiki

Files

T

tests / pytest (push) Successful in 6s

Details

docs: READMEs describe current behaviour, not history

Removes the decision logs, the dated rows, the strikethrough retirements and
the setup progress checkboxes from all four READMEs. A decision log records how
the system came to be; a reader needs to know how it is. The two had drifted
far enough apart that the docs asserted things the shipped config contradicted.

Corrected, all of which were stale rather than merely verbose:

- the architecture section described the source-repo workflow as self-contained
  and called the reusable workflows here "not actively called; may be stale".
  They are the pipelines; the source-repo workflow is a thin caller.
- `workflow_call` was recorded as abandoned, and the instance as having no orgs.
  Both pipelines run through cross-repo `workflow_call` under an org.
- tech-blogs was described as not yet initialised. It has published.
- ses and tech invocation sections claimed a self-contained workflow too.

Kept, rewritten as behaviour rather than as dated decisions, because they are
live operational constraints and not history:

- the callee workflow cache, why a `publish-*.yml` edit appears not to take,
  and the flush command with its `--no-deps` and `--pull` caveats
- why this repo has to stay public
- the `URL_TO_GITEA` / `PUBLIC_URL_TO_GITEA` split and what validates it
- host network mode, and that `kaniko-act` cannot be rebuilt by build-image.yml

Also documents what the renderer, its failure modes and its publish scope
actually are, which the decision logs had been standing in for, and adds the
architecture note that renderer code is cloned fresh per run while workflow
YAML is cached — the distinction that governs whether a change takes effect.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-09 17:39:28 +09:00

4.0 KiB

Raw Blame History

pipelines/ses

Publishes SES light novel pages from novoyuuparosk-wiki/ses-light-novel to https://wiki.novoyuuparosk.org under the SES: namespace.

Source-file contract (frontmatter and body conventions): SCHEMA.md
Cross-cutting setup (wiki URL, bot identity, runner, Gitea secrets/variables): repo root README

What the renderer does

YAML frontmatter parsing per SCHEMA.md
SES: title prefix — all pages live in the SES MediaWiki namespace
Pandoc-based markdown → wikitext body rendering
Auto-generated banner ({{Auto-generated|source=...|commit=<sha>}})
Category injection: [[Category:SES]] + [[Category:SES:<type>]] on every page; type from type: field, falling back to the file's parent directory name
Additional categories via optional categories list
MediaWiki bot API write with idempotency — no-op if wiki content matches generated output
Files without wiki.publish: true silently skipped
Pages with existing non-auto-generated content skipped (logged to stderr)

Not in scope (intentional):

Sibling/cross-page link resolution — write wikilinks directly in the markdown body
Companion file uploads

Source repo and branch convention

Source repo: novoyuuparosk-wiki/ses-light-novel. The pipeline triggers on push to master.

No branch convention enforced — work directly on master or use whatever branch workflow suits. There is no wip/ exclusion; wiki.publish: true is the only publishing gate.

Excluded paths (won't trigger the pipeline):

README.md, .gitignore, .claude/**

Invocation

novoyuuparosk-wiki/ses-light-novel/.gitea/workflows/publish.yml is a thin caller: it triggers, then uses: publish-ses.yml here, which clones both repos and runs publish.py.

Editing publish-ses.yml requires a runner cache flush before it takes effect; the renderer itself is cloned fresh every run. See Callee workflow cache in the root README.

Triggers:

push to master (path-filtered as above)
workflow_dispatch — manual trigger from the Gitea Actions UI

Publish scope

Every run publishes every file with wiki.publish: true; there is no diff detection. Writes are idempotent — the banner carries the commit SHA rather than a timestamp, so a re-run at the same commit rewrites nothing.

Environment (secrets and variables)

Name	Kind	Source	Purpose
`WIKI_API_URL`	variable	Gitea (cross-cutting)	MediaWiki action API endpoint
`WIKI_BASE_URL`	variable	Gitea (cross-cutting)	Wiki base URL
`WIKI_BOT_USER`	secret	Gitea (cross-cutting)	Bot login
`WIKI_BOT_PASSWORD`	secret	Gitea (cross-cutting)	BotPasswords value
`URL_TO_GITEA`	variable	Gitea (cross-cutting)	Runner-internal Gitea base URL, for cloning only
`PUBLIC_URL_TO_GITEA`	variable	Gitea (cross-cutting)	Public Gitea base URL, for the banner source link only
`FAPAT`	secret	Gitea (cross-cutting)	Full-Access PAT for cloning private repos
`SOURCE_REF`	env (set in workflow)	`github.sha`	Pushed commit SHA, used in banner and edit summary
`GITEA_REPO_URL`	env (set in workflow)	`PUBLIC_URL_TO_GITEA` + repo path	Source-file URL base for the banner link. Validated by `public_source_base()`: a loopback, mDNS or private-range host aborts the run rather than publishing an unreachable link

Dependencies

Job container image and its build are described in the root README. Python packages for this pipeline are in requirements.txt here; changing it triggers an image rebuild. Shared render and MediaWiki helpers live in lib/wiki.py at the repo root.

Wiki-side prerequisites

Template:Auto-generated must exist on the wiki. It is shared across all three pipelines; the wikitext source lives in pipelines/songs/template_auto_generated.wikitext.

4.0 KiB Raw Blame History