Repository navigation
ci: add protected release deployment entry point - #1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change
Add a single
releasebranch as the production publication target. Verification runs for pushes to bothmainandrelease, and for pull requests.vp run deploy:productionrequires a clean checkout at the current remotereleaseSHA, enforced branch protection with requiredverifyand pull requests, and successful GitHub verification for that exact SHA. It then runs full local verification and secret scanning before publishing the existing app and site through local Cloudflare authentication. No deployment credentials are added to GitHub.Validation
Application and site publish sequentially. A partial deployment must be checked and reported separately; no automatic data restore is performed.