Wiki title prefix policy
This commit is contained in:
@@ -215,6 +215,7 @@ topdata:
|
||||
managed_namespaces: [classes, feat, itemtypes, races, skills, spells, meta]
|
||||
deploy_manifest: .wiki_deploy_manifest.json
|
||||
deploy_edit_summary: Auto-generated from native builder
|
||||
title_prefix_min_length: 3
|
||||
|
||||
autogen:
|
||||
cache:
|
||||
@@ -332,6 +333,13 @@ instead. Updates and stale-page archives acquire a Westgate Wiki edit lock
|
||||
before saving, then send the returned `wikiEditLockToken` with the NodeBB post
|
||||
edit request.
|
||||
|
||||
For newly created NodeBB topics, `topdata.wiki.title_prefix_min_length`
|
||||
controls when the deployer prefixes the namespace in the topic title. The
|
||||
default is `3`, so one- and two-character page titles are created as
|
||||
`Namespace: Title`, while titles with three or more characters keep the page
|
||||
title alone. Existing bot-managed pages with older prefixed titles are renamed
|
||||
on later deploy passes when their current title no longer matches this policy.
|
||||
|
||||
`build-changelog` renders a release changelog from tagged pushes. Pull-request
|
||||
style commits keep their PR links and authors from the Gitea API; direct pushes
|
||||
are rendered as commit links using the commit author. It defaults to
|
||||
|
||||
Reference in New Issue
Block a user