Repository navigation
Conversation
This branch was successfully deployed
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.
The initial production cutover changes only the
wwwCNAME. This records the current Unbounce and Namecheap forwarding baseline, keeps the existing apex forwarding and all mail records untouched, and defines rollback as restoringwwwtounbouncepages.com.It also records the accepted production commit and successful deployment. Unbounce remains available as a rollback target and is not cancelled or deleted by this migration. The runbook explicitly notes that rollback depends on Unbounce continuing to retain and serve the suspended project.
Validation: repository formatting and whitespace checks pass.