From 78009b4902f7aaaba609aaa7d3c940848dfd2485 Mon Sep 17 00:00:00 2001 From: Naruto TAKAHASHI Date: Sat, 1 Aug 2026 20:16:16 +0900 Subject: [PATCH] ci: publish the docs site on release rather than on push to main Deploying on every merge to main puts the published site ahead of the release the SpriteStudio Docs portal links to, so readers can reach documentation for behavior that has not shipped. Tying the deploy to `release: published` keeps the site and the portal's "coming soon" gate in step. Matches SSPlayerForUnity / SSPlayerForRenPy / SSConverterGUI, which were already release-triggered. `workflow_dispatch` still forces a deploy, and pull requests keep building with --strict (the deploy job is gated on `github.event_name != 'pull_request'`), so broken links and nav gaps are still caught per PR. --- .github/workflows/pages.yml | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/.github/workflows/pages.yml b/.github/workflows/pages.yml index ab1d296..fcd1acc 100644 --- a/.github/workflows/pages.yml +++ b/.github/workflows/pages.yml @@ -3,16 +3,13 @@ name: Publish docs via GitHub Pages # Build the MkDocs site and deploy it to GitHub Pages via the artifact method # (no gh-pages branch) — matching SSPlayerForWeb / SSPlayerForRenPy. # -# Triggers stay on the docs hot path: push to main and manual dispatch deploy, -# while PRs only build with --strict to catch broken links / nav gaps. +# The published site is tied to releases, not to merges: a published release and a +# manual dispatch deploy, while PRs only build with --strict to catch broken links / +# nav gaps. This keeps the docs site in step with the release the portal links to, +# rather than running ahead of it on every merge. on: - push: - branches: - - main - paths: - - 'docs/**' - - 'mkdocs.yml' - - '.github/workflows/pages.yml' + release: + types: [published] pull_request: paths: - 'docs/**'