{{ message }}
Repository navigation
ci: avoid redundant deployment history - #2
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
1 participant
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.
Intent
Keep protected environment access without accumulating redundant GitHub deployment history. The publisher App already supplies verified preview links and publishing results.
Changes
Set
deployment: falsefor preview, production, and cleanup jobs, and remove unused environment URLs. Named environments and their secrets and branch policies remain enforced. Retention continues to operate on Cloudflare's authoritative deployments. This uses GitHub's documented environment setting.Validation
python -B -m unittest discover -s testsactionlint -no-color .github/workflows/publish.yml .github/workflows/ci.yml .github/workflows/cleanup.ymlzizmor --no-progress --format plain .github/workflowsgit diff --checkNotes
The environments currently use branch policies and have no custom deployment protection Apps. Such Apps require deployment objects and would be incompatible with this setting. No reviewers were requested.