Getting Started with Mergeway
Introduce Mergeway workspace concepts, building blocks, and validation flow for new users.
Mergeway’s goal is to make metadata a commodity putting it in the open and treating it as code. Instead of juggling spreadsheets or custom scripts, you describe entities in YAML/JSON, run a quick validation, and catch broken references before they reach production. By storing metadata as code, changes become a simple patch.
mergeway-cli init writes a starter mergeway.yaml into your working directory so you can begin defining entities immediately.json_schema) so teams can reuse specs.list, get, create, update, and delete operate on local YAML/JSON files, respecting identifier fields defined in schemas and inline data.mergeway-cli fmt emits canonical structure and rewrites files in place (use --stdout to preview changes) to keep diffs clean.mergeway-cli entity show and mergeway-cli config export surface normalized schemas or derived JSON Schema for documentation and automation.Updates land in the Changelog. File GitHub issues for questions, bugs, or requests.
For a more general introduction to Mergeway, visit the homepage
Introduce Mergeway workspace concepts, building blocks, and validation flow for new users.
Reference for Mergeway CLI commands, global flags, and usage.
Task-focused guides for common Mergeway workflows and integrations.