Skip to content

[P2] Decision: keep .nuke/ directory convention or migrate to .fallout/ #29

Description

@ChrisonSimtian

Question

`.nuke/temp`, `.nuke/parameters.json`, `.nuke/build.schema.json` etc. are hard-coded inside `Nuke.Common` as the standard NUKE working directory.

Three options:

  1. Keep `.nuke/` — the directory name becomes a historical artifact, like how Mercurial repos still have `.hg` after rebranding. Zero migration cost for consumers. Cheap.

  2. Migrate to `.fallout/` — clean rebrand. Every consumer needs to move files. Source code reads from new path; ideally also has back-compat fallback that warns.

  3. Hybrid — read from both, write to `.fallout/`, warn if `.nuke/` is found.

Recommendation

Option 3 for two release cycles, then drop `.nuke/` support. Captures the symbolic break without inflicting a forced migration.

Out of scope here

Implementing the chosen option. This issue is the decision; the implementation issue follows.

Done when

  • Decision documented in this issue
  • Implementation issue opened with the chosen approach

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions