Skip to content

Refresh canonical deploy on repository visibility changes #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
sepo-agent-app wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Refresh canonical deploy on repository visibility changes #30

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f1a42bb
Trigger canonical deploy on repo visibility changes
sepo-agent Aug 13, 2026
a10e1ba
Use public: event for publicize; defer privatize to #31
sepo-agent Aug 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions .github/workflows/agent-deploy-site-main.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,18 @@ on:
push:
branches: [main]
workflow_dispatch:
# A private->public visibility flip must refresh the canonical deployment.
# The preview-api re-derives repo identity from the OIDC token and re-reads
# GitHub's current visibility on every canonical deploy, rewriting both the
# preview-registry record (isPrivate) and the R2 META (visibility). Without a
# trigger those snapshots only update on the next push to main, so a
# newly-public repo stays behind the private-site gate until then.
#
# `public` is the only repository-visibility transition GitHub Actions exposes
# as an `on:` event; it fires on private->public only and takes no `types`.
# The reverse public->private (privatize) transition has NO native Actions
# trigger and is NOT covered here -- it is tracked separately in #31.
public:

permissions:
id-token: write
Expand All @@ -19,6 +31,11 @@ concurrency:

jobs:
deploy:
# The public (private->public) event fires against the default branch, so
# github.ref is refs/heads/main and this guard accepts it alongside push
# and workflow_dispatch while still deploying only main. The concurrency
# group above also keys on github.ref, so a visibility event shares the
# canonical-site group and cancel-in-progress behavior.
if: vars.AGENT_ENABLED != 'false' && github.ref == 'refs/heads/main'
runs-on: ubuntu-latest
steps:
Expand Down
Loading