Skip to content

ci: publish the docs site on release rather than on push to main #249

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Naruto merged 1 commit into from
Aug 1, 2026
Merged

ci: publish the docs site on release rather than on push to main #249

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 6 additions & 9 deletions .github/workflows/pages.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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/**'
Expand Down
Loading