Skip to content

PROTM-1348: Default to no data for branch data mode#173

Open
sandshoes wants to merge 2 commits into
mainfrom
protm-1348
Open

PROTM-1348: Default to no data for branch data mode#173
sandshoes wants to merge 2 commits into
mainfrom
protm-1348

Conversation

@sandshoes

Copy link
Copy Markdown
Contributor

Branch data mode automatically fetches the last-partition. It should really default to no data this is what we've done here

@sandshoes sandshoes requested a review from manumartinm July 7, 2026 16:02
Comment thread CHANGELOG.md

## [Unreleased]

### Added

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how should I document the changelog?

@sandshoes sandshoes requested review from eclbg and jordiori July 7, 2026 16:08
Comment thread CHANGELOG.md Outdated

### Changed

- `branch_data_mode` now defaults to `"none"`: cloud branches are created empty unless `"last_partition"` is set explicitly. This restores the pre-`branch_data_mode` behavior and avoids branch-creation timeouts on workspaces with large partitions. Set `branch_data_mode: "last_partition"` in your config to keep copying production data into branches.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Up until which version did we have this behaviour? It will be useful to include this here so users can quickly see if their default will change or not.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agree updated the changelog mentioning the span of versions where the default changed

@eclbg

eclbg commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

How does this compare to the default behaviour in the CLI? Is that also no data? I get this affects only cloud branches as local branches are (and already were) never seeded with data other than perhaps fixtures. Is that correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants