ecn_create
Create a new Engineering Change Notice (ECN) for a project. Specifies ECN details like type, severity, and disposition, then commits to a branch or opens a pull request.
Instructions
Create a new Engineering Change Notice (ECN).
The API clones the repo, creates the ECN file in ECO/, commits,
and optionally pushes to a branch or creates a PR.
For local projects, use: parts project ecn create --id ECN-021 ...
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | Source Parts project ID or git repo URL | |
| ecn_id | Yes | ECN identifier (e.g. 'ECN-021') | |
| title | Yes | ECN title describing the issue | |
| ecn_type | Yes | One of: Design Constraint, Assembly Note, BOM Change, Schematic Change, Process Change | |
| severity | Yes | One of: CRITICAL, HIGH, MEDIUM, LOW | |
| disposition | Yes | One of: REQUIRED, RECOMMENDED, OPTIONAL | |
| category | No | Optional category (e.g. Electrical, Mechanical, Thermal) | |
| author | No | Author name (defaults to 'Unknown') | |
| source | No | Source reference | |
| affected | No | Affected components | |
| body | No | ECN body content (markdown). If empty, a template is used. | |
| create_pr | No | If True, create a pull request with the change | |
| branch | No | Target branch for the commit (default: main) |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||