Restrict GitHub Pages deploys to main pushes only

[Copilot]

Monthly release activity was triggering the Pages deploy workflow via tag events, which could overwrite or destabilize the live site. This change narrows deployment triggers so only main pushes can publish to GitHub Pages.

• Deploy trigger scope

  • Removed tag-based trigger (v*) from .github/workflows/deploy.yml.
  • Keeps pull-request builds intact while preventing release-tag deployments.

• Deploy job guardrail

  • Tightened the deploy job condition to allow publishing only on refs/heads/main.
  • Eliminates tag-path deploys even if additional push events are introduced later.

on:
  push:
    branches: [ main ]
  pull_request:
    branches: [ main ]

# ...
deploy:
  if: github.event_name == 'push' && github.ref == 'refs/heads/main'

[Copilot]

Pull request overview

This PR tightens the GitHub Actions deployment workflow for GitHub Pages so publishing can only occur from direct pushes to the main branch, preventing release tag activity from triggering (and potentially overwriting) the live Pages site.

Changes:

• Removed the push.tags: ['v*'] trigger from the Pages deploy workflow.
• Updated the deploy job if: condition to only allow deployments on push events where github.ref == 'refs/heads/main'.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.