Skip to content

Extract the clone default org into the default_org setting - #135

Open
JPDuchesne wants to merge 1 commit into
mainfrom
jpd/clone-default-org-setting
Open

Extract the clone default org into the default_org setting#135
JPDuchesne wants to merge 1 commit into
mainfrom
jpd/clone-default-org-setting

Conversation

@JPDuchesne

Copy link
Copy Markdown
Contributor

Summary

  • Dev::Clone::RepoSpec no longer hardcodes DEFAULT_ORG = "d3mlabs": bare <repo> targets expand under the new nilable default_org settings key (DEV_DEFAULT_ORG ENV over ~/.config/dev/config.yml), injected by Clone::Accessor.
  • A bare target with no configured org raises RepoSpec::MissingDefaultOrgError with a message naming both the settings key and the ENV override; explicit <org>/<repo> targets need no configuration.
  • dev clone DESC and README updated — part of the org-agnostic dev doctrine (settings are the org-content seam, alongside baseline_repo in Deployment scheme: layered settings + the Brewfile host contract #133).

Verification

  • 938 tests, 0 failures; rubocop and srb tc clean.
  • New coverage: settings key (file / ENV-override / unset-nil), parse with and without a default org, the typed error surfacing through the accessor.

Made with Cursor

dev is public and hardcodes no org content, so RepoSpec's hardcoded
d3mlabs falls to a new nilable default_org settings key (ENV
DEV_DEFAULT_ORG over the config file). A bare `dev clone <repo>` with
no configured org raises a typed error naming both remediations.

Co-authored-by: Cursor <cursoragent@cursor.com>
@codecov

codecov Bot commented Aug 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

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.

1 participant