pkgdown deploys from every branch push #234

pkgdown.yaml triggers on [push, pull_request, workflow_dispatch], and its deploy step runs whenever github.event_name != 'pull_request'. So every push to any branch deploys that branch's site to the root of gh-pages (clean: false). Feature branches overwrite the published devel docs until the next devel push.

This showed up on 2026-10-16: creating RELEASE_3_23 on GitHub and pushing fix/release-3.23-vignette-network (#233) deployed 3.23 release docs at the same time as the devel deploy for #232. Devel had to be redeployed by hand afterwards.

Separately, R-CMD-check.yaml only runs for pushes and PRs on main and devel. PRs into RELEASE_* (like #233) get pkgdown and no R CMD check.

Proposed:

• In pkgdown.yaml, deploy only on pushes to devel, for example if: github.event_name == 'push' && github.ref == 'refs/heads/devel' (or include main if it should still publish). Optionally keep building on other branches as a smoke test, without deploying.
• Optionally, limit the push trigger to branches: [devel] so feature-branch pushes don't build twice (push + pull_request).
• In R-CMD-check.yaml, add RELEASE_* to the pull_request (and maybe push) branch filters. The bioc-check job uses bioconductor_docker:devel. For release branches it should use the matching release image (for example RELEASE_3_23), or derive it from github.base_ref.

🤖 Generated with Claude Code