feat(deploy): default CFP_DATA_BRANCH to published#69
Merged
Conversation
The data repo now carries a dedicated `published` branch (built from `empty` + merged `legacy-import`) that's the long-term runtime branch. `fixture` reverts to its original role — a small handful of curated test records for local development. Unblocked by #66 (PR #68): the entrypoint + Node reconciler now use an explicit fetch refspec, so switching `CFP_DATA_BRANCH` between branches no longer trips the single-branch-clone limitation that bit us earlier. The branch is overridable per-pod via the existing `CFP_DATA_BRANCH` env var — overlays can point a debug deployment at `fixture` or `legacy-import` without touching the base. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Closes #59 follow-up. Switches the deployed instance's default data branch to
published(which the importer-outputlegacy-importbranch merges into).Unblocked by #68: the new Node-side reconciler uses explicit fetch refspecs (
+refs/heads/${branch}:refs/remotes/origin/${branch}), so the single-branch-clone limitation that previously broke switching no longer applies.Per-pod override remains via the
CFP_DATA_BRANCHenv var — overlays can keep a debug deployment onfixture(~4 records) orlegacy-import(raw snapshot, no merged runtime writes).🤖 Generated with Claude Code