workflow update

Author: aboyle

.github/workflows/site.yml

@@ -5,10 +5,14 @@ on:
     branches:
       - main
       - master
+    paths:
+      - "bibliography/publications.bib"
   pull_request:
     branches:
       - main
       - master
+    paths:
+      - "bibliography/publications.bib"
   workflow_dispatch:
 
 concurrency:

DEVELOPMENT.md

@@ -72,7 +72,7 @@ Add a regression test whenever a content mistake causes a build failure. For exa
 
 ## GitHub Actions workflow
 
-`.github/workflows/site.yml` runs on pushes and pull requests targeting `main` or `master`, and can be started manually.
+`.github/workflows/site.yml` runs automatically only when `bibliography/publications.bib` changes in a push or pull request targeting `main` or `master`. It can also be started manually with **Run workflow** in GitHub Actions.
 
 The build job:
 
@@ -88,6 +88,8 @@ The deploy job runs only outside pull requests and publishes the artifact to the
 
 In repository **Settings → Pages**, set the publishing source to **GitHub Actions**. The workflow supports either `main` or `master` as the default branch.
 
+Because the workflow is path-limited, changes that do not modify `bibliography/publications.bib` do not start an automatic Pages deployment. After a news, people, CSS, layout, or other site-only update, start this workflow manually unless a separate general site-deployment workflow is configured.
+
 A commit created by `GITHUB_TOKEN` does not need a second workflow run: the active run builds and deploys from the regenerated working tree after committing it.
 
 ## Editing publication sources in GitHub

PUBLICATIONS.md

@@ -70,7 +70,7 @@ Keys must match `^[A-Za-z][A-Za-z0-9]*$`, be unique without regard to filename c
 
 6. Commit the BibTeX, sidecar, generated `_papers` record, and `pub.bib`.
 
-The GitHub Actions workflow performs the same generation and will commit changed generated files after a direct push.
+When `bibliography/publications.bib` changes, the GitHub Actions workflow performs the same generation and commits changed generated files after a direct push. The workflow can also be started manually.
 
 ## Minimal sidecar
 

README.md

@@ -46,4 +46,4 @@ scripts/build_site.sh
 
 ## Automated deployment
 
-`.github/workflows/site.yml` regenerates publications, runs the test suite, builds the Jekyll site, and deploys it to GitHub Pages. On a direct push, it commits changes to `_papers/` and `pub.bib` when the BibTeX or sidecar sources produce new output. Pull requests must include current generated files.
+`.github/workflows/site.yml` runs automatically only when `bibliography/publications.bib` changes, then regenerates publications, runs the test suite, builds the Jekyll site, and deploys it to GitHub Pages. On a direct push, it commits changes to `_papers/` and `pub.bib`. The workflow remains available through manual dispatch for other site deployments.

tests/test_workflow.py

@@ -20,6 +20,12 @@ def test_workflow_has_push_pull_request_and_manual_triggers(self) -> None:
         self.assertIn("pull_request", triggers)
         self.assertIn("workflow_dispatch", triggers)
 
+    def test_automatic_runs_are_limited_to_the_bibliography_file(self) -> None:
+        triggers = self.workflow["on"]
+        expected_paths = ["bibliography/publications.bib"]
+        self.assertEqual(triggers["push"]["paths"], expected_paths)
+        self.assertEqual(triggers["pull_request"]["paths"], expected_paths)
+
     def test_workflow_regenerates_and_checks_publications(self) -> None:
         self.assertIn("python scripts/build_publications.py --strict", self.text)
         self.assertIn("python -m unittest discover -s tests -v", self.text)