post_merge_setup

You can automate post-merge dependency installation and migrations by configuring a post-merge script. This process automatically runs the script after a merge to install dependencies, execute migrations, and rebuild environments, ensuring your project maintains a healthy state.

Reconciling running workflows with .replit configuration is handled automatically during post-merge setup. The process syncs workflow states with the configuration file to ensure environmental consistency and surfaces clear reconciliation errors if discrepancies occur.

Yes, you can enforce a configurable timeout for post-merge scripts. The setup allows you to define script paths and timeouts, ensuring that if a script exceeds its limit or goes missing, the system safely handles it and reports the error.

Post-merge setup safely handles missing scripts by detecting their absence and reporting clear setup errors. Instead of failing silently, the system enforces the configured script path and surfaces the issue to ensure a reliable merge workflow.

Yes, you need to configure the post-merge script path in your project's .replit file before running a test merge. This setup ensures the workflow can locate the script, apply the correct timeout, and properly reconcile dependencies and migrations.

Workflow states become inconsistent after merging when running environments are not reconciled with the .replit configuration. Automating post-merge setup syncs these states, runs migrations, rebuilds dependencies, and reports errors to restore consistency.