From 061b58764fa3a729b74e74f78b59ed1074b7daae Mon Sep 17 00:00:00 2001 From: Howard Lewis Ship Date: Wed, 2 Sep 2026 18:45:29 -0700 Subject: [PATCH 1/2] ci: rebuild the manual on every push to main Fires the same repository_dispatch at Dialog-IF/manual that release.yml already sends, so a plain merge to main keeps the published manual in sync with docs/, not just tagged releases. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01RTppFtoRZ3ZmWYF14xDiXX --- .github/workflows/rebuild-manual.yml | 34 ++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 .github/workflows/rebuild-manual.yml diff --git a/.github/workflows/rebuild-manual.yml b/.github/workflows/rebuild-manual.yml new file mode 100644 index 0000000..3ecb57e --- /dev/null +++ b/.github/workflows/rebuild-manual.yml @@ -0,0 +1,34 @@ +name: Rebuild Manual + +# The Dialog manual (Dialog-IF/manual) pulls this repo's docs/ directory in as an Antora content +# source, so every push to main can leave the published manual stale. This fires a +# repository_dispatch at that repo to rebuild and redeploy it. release.yml fires the same event +# after a tagged release; this covers the far more common plain merge to main. +# +# Needs a MANUAL_REBUILD_TOKEN repository secret - a token with Contents: read and write on +# dialog-if/manual (classic PAT: repo scope). See that repo's README, "Triggering a rebuild from +# another repository". + +on: + push: + branches: [main] + workflow_dispatch: + +permissions: + contents: read + +# Coalesce a burst of merges into a single rebuild rather than one per push. +concurrency: + group: rebuild-manual + cancel-in-progress: true + +jobs: + rebuild-manual: + runs-on: ubuntu-latest + steps: + - name: Trigger manual rebuild + uses: peter-evans/repository-dispatch@v3 + with: + token: ${{ secrets.MANUAL_REBUILD_TOKEN }} + repository: dialog-if/manual + event-type: rebuild-manual From 470bc1d2e4043806d328978e5428c36ce9c2d40d Mon Sep 17 00:00:00 2001 From: Howard Lewis Ship Date: Wed, 2 Sep 2026 18:46:56 -0700 Subject: [PATCH 2/2] ci: only rebuild the manual when docs/ changes A code-only merge produces an identical site. workflow_dispatch stays available for a forced rebuild. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01RTppFtoRZ3ZmWYF14xDiXX --- .github/workflows/rebuild-manual.yml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.github/workflows/rebuild-manual.yml b/.github/workflows/rebuild-manual.yml index 3ecb57e..5ba24af 100644 --- a/.github/workflows/rebuild-manual.yml +++ b/.github/workflows/rebuild-manual.yml @@ -1,9 +1,10 @@ name: Rebuild Manual # The Dialog manual (Dialog-IF/manual) pulls this repo's docs/ directory in as an Antora content -# source, so every push to main can leave the published manual stale. This fires a +# source, so a merge to main that touches docs/ can leave the published manual stale. This fires a # repository_dispatch at that repo to rebuild and redeploy it. release.yml fires the same event -# after a tagged release; this covers the far more common plain merge to main. +# after a tagged release; this covers the far more common plain merge to main. Scoped to docs/ - +# a code-only merge produces an identical site, so there's nothing to rebuild. # # Needs a MANUAL_REBUILD_TOKEN repository secret - a token with Contents: read and write on # dialog-if/manual (classic PAT: repo scope). See that repo's README, "Triggering a rebuild from @@ -12,6 +13,7 @@ name: Rebuild Manual on: push: branches: [main] + paths: ['docs/**'] workflow_dispatch: permissions: