Add workflow to trigger python-docs-pdf builds on Doc/ changes

[Copilot]

Automate python-docs-pdf repository builds when documentation is updated in cpython. When commits to main or 3.* branches modify Doc/** paths, trigger the downstream workflow via repository_dispatch.

Changes

• New workflow .github/workflows/trigger-docs-pdf.yml:

  • Triggers on push to main and 3.* branches with Doc/** path filter
  • Sends repository_dispatch event with cpython_docs_updated type to m-aciek/python-docs-pdf
  • Payload includes branch name, repository, commit SHA, and message
  • Uses jq for JSON construction to prevent injection attacks

• Documentation .github/workflows/README-trigger-docs-pdf.md:

  • Setup instructions for required DOCS_PDF_TRIGGER_TOKEN secret (PAT with workflow trigger permissions)
  • Configuration needed in target repository to accept dispatch events

Required Setup

This repository: Add DOCS_PDF_TRIGGER_TOKEN secret containing a PAT with repo or public_repo scope.

Target repository (m-aciek/python-docs-pdf): Add repository_dispatch trigger to build.yaml:

on:
  repository_dispatch:
    types: [cpython_docs_updated]

Then reference the branch from the payload:

- uses: actions/checkout@v6
  with:
    repository: python/cpython
    ref: ${{ github.event.client_payload.branch }}

Original prompt

Please modify the workflow files in a way that:

• when a commit lands on the main or on the stable branch
• this commit modifies a path with Doc/ prefix
• then https://github.com/m-aciek/python-docs-pdf/blob/main/.github/workflows/build.yaml workflow (in https://github.com/m-aciek/python-docs-pdf) repository should be triggered for that branch

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.