Skip to content

fix: preserve effective config and parse init options without weakening settings #21

Description

@chtnnh

Problem

init starts from built-in defaults instead of the effective home configuration, and absent CLI options are treated as explicit false values. A plain re-init can disable an existing requireTrailer setting; --require-trailer true is also parsed incorrectly.

Scope

Use effective configuration as the initialization baseline and make option parsing tri-state and strictly typed.

Acceptance criteria

  • Home defaults survive first repo initialization unless explicitly overridden.
  • Re-running init preserves omitted boolean settings.
  • --require-trailer true and false behave as documented.
  • Invalid boolean values fail rather than silently selecting a value.
  • Tests cover home/repo precedence and repeated initialization.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions