trunk-plan

A trunk-based migration plan can be previewed by evaluating a trunk-migration config file against a schema. This generates a detailed, non-modifying execution plan listing create, modify, and delete operations for review before execution.

A non-modifying execution plan is a detailed output generated from a trunk-migration config that lists files to create, modify, and delete without executing actual changes. It enables repository-wide planning and review workflows across API versioning, Auth0, NuGet, UI tests, and EF migrations.

You validate a trunk-migration config by running it through a planning tool that checks the config against the trunk migration schema. This process surfaces dependencies and risks across API versioning, Auth0, NuGet, UI regression tests, and EF migrations before any changes are made.

Yes, you can generate a unified migration plan for EF migrations and API versioning together. The planning process evaluates five decision trees—including Auth0, NuGet, and UI regression tests—to surface dependencies and risks across your repository in a single non-modifying output.

No, the trunk migration planning process does not execute file changes automatically. It produces a detailed plan listing files to create, modify, and delete, ensuring no actual changes are made and enabling safe review before you apply any modifications.