.github

Org-level configuration for GWAC-MPPR.

• profile/README.md — the README shown on the organisation page.
• .github/workflows/quarto-slides.yml — reusable workflow that builds and publishes the slides repos.

Using the slides workflow

A slides repo's .github/workflows/publish.yml reduces to a caller:

on:
  workflow_dispatch:
  push:
    branches: main

name: Render and Publish

jobs:
  build-deploy:
    permissions:
      contents: write
    uses: GWAC-MPPR/.github/.github/workflows/quarto-slides.yml@v1
    with:
      use-renv: true
      release-tag: slides-2026

The doubled .github/.github/ is correct: the first is the repository name, the second the directory inside it.

permissions belongs on the calling job. Permissions are set by the caller and the callee's token is the intersection of the two, so a caller that omits contents: write fails at the gh-pages push with a 403. GITHUB_TOKEN reaches the workflow automatically; secrets: inherit is only needed once a custom secret is involved.

Inputs

Input	Default	Notes
use-renv	false	true restores from renv.lock; false installs rmarkdown and knitr.
release-tag	required	Release the PDF is attached to, e.g. slides-2026. The release must already exist.
quarto-version	1.9.37	Keep in step with the Quarto that generated the committed _freeze.
qmd-path	slides.qmd	The PDF asset name is derived from this.

Versioning

Callers pin @v1 rather than @main, so an edit here does not change every repo's pipeline unreviewed. After changing the workflow, move the tag deliberately:

git tag -f v1 && git push -f origin v1

Each repo still needs its own _quarto-pdf.yml profile declaring the beamer format. Keeping beamer out of the deck's own front matter stops quarto publish gh-pages sweeping the rendered PDF into that branch.