Skip to content

Add label-gated Cloudflare preview deployments - #107

Draft
joaomarcoscrs wants to merge 1 commit into
mainfrom
joao/cloudflare-preview-automation
Draft

Add label-gated Cloudflare preview deployments#107
joaomarcoscrs wants to merge 1 commit into
mainfrom
joao/cloudflare-preview-automation

Conversation

@joaomarcoscrs

Copy link
Copy Markdown
Collaborator

Description

Adds opt-in Cloudflare Pages previews without placing Cloudflare credentials or private infrastructure details in the public repository.

A maintainer-applied cloudflare-preview label creates or updates a synthetic preview/pr-<number> branch at the exact pull request head. Cloudflare builds only those branches, reports a native check run, and a second workflow updates one sticky pull request comment with the stable preview URL or failure details. Removing the label or closing the pull request deletes the synthetic branch.

The workflows never check out pull request code and receive no Cloudflare secrets. The 134 MB horse-trail video is excluded from the Pages artifact and resolved from the public R2 origin owned by roboflow/roboflow-infra#2542. Production remains on GitHub Pages.

Type of Change

  • New feature
  • Breaking change
  • Documentation or example update
  • Refactor or maintenance
  • Performance improvement

Validation

  • Tests added or updated where behavior changed

  • Documentation updated where the public API or workflow changed

  • Screenshots or recording attached for visual changes

  • npm run verify passed, including 845 Vitest tests, package smoke tests, package boundaries, all package builds, demo, and benchmark builds.

  • npm run pages:build passed. The deployed artifact excludes the 134 MB horse video and contains no file above Cloudflare Pages' 25 MiB limit.

  • actionlint passed for both new workflows.

  • git diff --check passed.

Notes For Reviewers

This remains a draft until the private infrastructure PR is applied, the horse-trail object is uploaded to R2, and the cloudflare-preview label is created. The new workflows must be present on the default branch before they can be exercised end to end on a later pull request.

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.

1 participant