CI: docs reach the public repo after every sync, and build no release there

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
tthandClaude Opus 5.5 committed 2026-11-17 13:15:29 +01:00
1 parent 41d3ba93ea
commit 7949fb4274
1 file changed
+10 -2
+10 -2
View File
@@ -9,8 +9,11 @@
# instalace_repeateru, regiony), PUB_FLAGS below. They apply to a node with
# no saved settings (fresh, or after an erase); a reflash keeps what is set.
#
# Runs on every push to main -- the export pushes there only after an
# upstream merge (private repo, tth-upstream-sync) -- and by hand.
# Runs on a push to main that touches the firmware -- the export pushes there
# after every upstream sync (private repo, tth-upstream-sync) -- and by hand.
# Documentation, the enclosure and CI files alone build nothing (paths-ignore):
# a release would only make every -ota node update itself to the same code.
# tools/ is NOT ignored: build_version.py and ota_ramlib.py are build inputs.
# Release tag v1.18.0+tth.<commit date>[.n] (the n-th release of that day),
# titled "v1.18.0+tth · 12. 11. 2026"; assets carry the tag in their names, the
# body the version the node reports (`ver`: v1.18.0-tth<sha>). Until 12. 11.
@@ -38,6 +41,11 @@ name: pub-release
"on":
push:
branches: [main]
paths-ignore:
- "**/*.md"
- "docs/**"
- "hardware/**"
- ".github/**"
workflow_dispatch:
inputs:
ref: