railway-template

To sync upstream commits to a Railway deployment fork, this Skill replays each commit individually from the parent repository. It then automatically applies necessary Railway adaptations to ensure the deployment remains functional.

The best way to resolve merge conflicts in a Railway template is by prioritizing Railway-specific modifications. This Skill provides logic to manage conflicts, ensuring custom configurations are preserved while integrating upstream features.

Automated upstream synchronization works by replaying commits from the upstream NanoClaw repository one by one. It automatically creates adaptation commits to re-apply Railway-specific changes after upstream modifications are integrated.

Yes, you can preserve Railway-specific configurations when syncing upstream updates. The Skill manages conflicts between upstream changes and Railway modifications to files like src/config.ts and src/env.ts to maintain functionality.

You need to run a Railway template sync when you want to integrate new features and bug fixes from the parent NanoClaw repository. This ensures your custom Railway deployment stays continuously up-to-date without manual merging.