--- title: "Workflow editor & Git workflow | Darwinium" slug: "journey-lifecycle-management" description: "Use Workflows to edit journey configuration, understand its files and move a reviewed revision through build and deployment." updated: 2026-10-16T09:37:17Z published: 2026-10-16T09:37:17Z canonical: "docs.darwinium.com/journey-lifecycle-management" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.darwinium.com/llms.txt > Use this file to discover all available pages before exploring further. # Workflow editor & Git workflow **Workflows** is the portal's editing workspace for the selected node's journey repository. Use it to define the interactions to process, map their data and configure profiling, rules, features, models and integrations. [Nodes & environments](/docs/nodes) explains which environment you are editing. The workspace uses an embedded Visual Studio Code editor with Explorer, Source Control and a terminal. You can use visual editors for common tasks and edit the underlying files when you need more control. ## Open the right editor Open a file from **Explorer**, rather than its change comparison in Source Control, when you want the normal editor. | File or tool | What it controls | | --- | --- | | `*.journey.yaml` | A journey's steps, triggers, mappings and workflows; opens the journey editor | | `journeys.yaml` | Which journey files are included in the build, with build-target configuration | | `*.feature.yaml` | A set of features used by rules and models | | `*.rules` | Rules, signals and rule-based scoring | | `*.strategy` | Decision-strategy logic | | `*.snippet` | Reusable configuration that imported journey templates expand into | | Source Control | Changes, commits and synchronization with the repository | Files such as rules and snippets must also be referenced where they are used. Merely creating a file does not make it execute on a step. ## Choose how to start - **Discover website interactions:** open [Record and update journeys](/docs/journey-recorder), walk through the site or use the available AI exploration, then review and update the journey. - **Define the flow yourself:** [Create a journey](/docs/creating-and-editing-journeys), then [configure steps](/docs/creating-and-editing-steps). - **Add another service or shared configuration:** [Install a Marketplace integration](/docs/marketplace-install-an-integration) or [make your own integration](/docs/integrations-1). - **Change risk assessment:** start with [How decisioning works](/docs/decisioning-overview), then use the feature, rule and model editors. A typical repository contains: ```text journeys.yaml authentication.journey.yaml src/ authentication.feature.yaml authentication.rules authentication.strategy snippets/ customer_account_risk.snippet README.md ``` Follow the file paths used by your repository. Journey files must be included in the build, and references must point to the files you intend to use. ## Understand what becomes active | Stage | Result | | --- | --- | | Edit and save | Your workspace files change. | | Review and commit | Git records a revision of the configuration. Synchronize it using your team's repository workflow. | | Build | Darwinium validates and prepares the selected configuration. Check failures before deployment. | | Deploy | The selected revision is applied to the intended node and targets. | | Verify | Test the application behavior and inspect the resulting events. | A saved file or successful build is not proof that the revision is deployed. In **Deployments**, check the revision and its deployment status. If your organization uses automated deployment, follow that pipeline's controls and verify its result. Use branches and reviews according to your team's process. [Git repository access](/docs/repository-access) explains how authorized users can work with the repository outside the portal. ## Check the completed change Follow [Deployment confirmation](/docs/deployment-confirmation), perform the intended interaction in a test environment and inspect it in [Investigations](/docs/investigations-overview). Confirm both the data and the customer-visible behavior. [Your first successful event](/docs/quick-start) provides a guided example.