Skip to content

Add workflow to redeploy site on release publish - #1

Merged
devnull03 merged 1 commit into
mainfrom
add-site-redeploy-workflow
Jun 7, 2026
Merged

devnull03 merged 1 commit into
mainfrom
add-site-redeploy-workflow

Conversation

@devnull03

Copy link
Copy Markdown
Owner

Adds .github/workflows/redeploy-site-on-release.yml on the default branch.

When a release is published, it dispatches the site branch's deploy-site.yml
so the build-time-rendered releases page refreshes. It must live on main
because release events only fire for workflows on the default branch.

🤖 Generated with Claude Code

When a release is published, dispatch the site branch deploy-site.yml so the build-time-rendered releases page refreshes. Lives on the default branch because release events only fire for workflows on main.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings June 7, 2026 10:40
@devnull03
devnull03 merged commit 9cc283b into main Jun 7, 2026
3 checks passed
@devnull03
devnull03 deleted the add-site-redeploy-workflow branch June 7, 2026 10:41

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a GitHub Actions workflow on the default branch to redeploy the site branch whenever a GitHub Release is published, ensuring the statically rendered releases page stays up to date.

Changes:

  • Introduces a release-triggered workflow (types: [published]) to kick off the site deployment.
  • Uses GitHub CLI to dispatch deploy-site.yml on the site branch.

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

Comment on lines +19 to +22
- name: Trigger site deploy
run: gh workflow run deploy-site.yml --ref site
env:
GH_TOKEN: ${{ github.token }}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants