post_merge_setup

Automating post-merge setup requires running a configured bash script from the project root that handles dependency installation and migrations. This ensures the repository remains in a consistent state by automatically reconciling workflows with the latest configuration immediately after merges.

Post-merge bash scripts hang during CI/CD automation when stdin remains open, prompting for user input. To force non-interactive execution and prevent hangs, stdin must be set to /dev/null, allowing the setup script to run without waiting for interactive feedback.

Reconciling workflows with .replit configuration involves stopping workflows removed from the config and restarting those that should still be running. This ensures runtime workflows match the latest project settings immediately after a merge is completed.

You can configure a hard timeout for post-merge setup scripts to prevent hanging tasks. When the execution overruns the configured timeout limit, the system issues a hard kill to terminate the process, ensuring your CI/CD pipeline does not stall indefinitely.

Debugging failed post-merge setup relies on deterministic reporting of setup and reconciliation errors. The system surfaces captured stdout, stderr, and specific log file paths immediately, providing actionable outputs to help you pinpoint and fix configuration issues fast.

Post-merge setup supports running scripts with the full Nix environment available on PATH. This ensures that all dependencies and tools defined in your Nix configuration are accessible during the non-interactive bash execution from the project root.