Microsite Restructure — Branch & Deployment Changes
Date: June 26, 2026
Team: CCG Contributors
Status: ✅ Completed
Owner: Syamala
Microsite changes are merged and deployed. main is now locked and read-only. develop is the new active working branch. All PRs must now target develop. Both Dev and Test environments are live.
🔍 What Are We Doing?
We've completed a structural overhaul of the Convenient Checkout microsite repository:
- All pending content and configuration changes merged into mainline
developis now the primary integration branchmainlocked — branch protection rules active- Dev and Test environments redeployed from
develop
This aligns with standard GitOps practices: environments always reflect reviewed, tested content.
🔖 Backup Tags
Safety backup tags were created before the restructure. Do not delete these.
| Tag | Source | Link | Purpose |
|---|---|---|---|
backup/develop | develop | View tag | Pre-merge snapshot |
backup/main | main | View tag | Pre-merge snapshot |
To revert the microsite to a pre-merge state, contact Support. Do not delete these tags without approval.
🚀 Deployment Status
Both environments are live from develop:
| Environment | URL | Status |
|---|---|---|
| Dev | docs.healthsafepay.com | ✅ Live |
| Test | developers.healthsafepay.com | ✅ Live |
After merging to develop, allow the CI pipeline 2–3 minutes to deploy. Validate on Dev before requesting sign-off.
🌿 Branch Strategy (Before vs. After)
| Branch | Before | After |
|---|---|---|
main | Active working branch | Locked · Read-only |
develop | Integration branch | Active working branch ✅ |
Rules now in effect:
| Rule | Detail |
|---|---|
Direct push to main | ❌ Blocked by branch protection |
| PRs | Must target develop |
main promotion | Controlled release process only |
| CI/CD trigger | develop → Dev & Test environments |
✅ What You Need To Do
1. Sync your local clone
git fetch origin
git checkout develop
git pull origin develop
2. Retarget any open PRs — update the base branch from main to develop before requesting review.
3. Update local tooling / scripts — if any CI scripts, deploy configs, or local Makefiles reference main as the default branch, update them to develop.
4. Validate your pages — after merge, confirm content renders correctly on Dev.
📚 Resources
| Resource | Link |
|---|---|
| Merchant Internal Content Guide | View Guide |
| Branch Protection Settings | (GitHub → Repo Settings → Branches) |
| Dev Environment | docs.healthsafepay.com |
| Test Environment | developers.healthsafepay.com |
🏁 Bottom Line
developis the one and only working branch.mainis locked.Raise all PRs against
develop→ validate on Dev → promote via release process. Backup tags are your safety net — do not delete them.
Questions? Reach out to Support.
🔗 Related
- Next step: main Branch Consolidation — Upcoming July 7