I've just been through an update in a deployed project of a template I'm developing. I had just pushed code to GitHub that updated a sub-directory, which only one service in the template builds from. Here's the user experience I just went through:

I clicked the "Sync Project" button, and was offered a modal to update service 1/13 which no source code had been updated for.

I clicked "Update service 1/13". The modal closed.

I clicked the "Sync Project" button, and was offered a modal to update service 2/13 which no source code had been updated for.

I clicked "Update service 2/13". The modal cosed.

I went through this process 13 times, until on the very last time by some tragic irony, I was given the option to "Update service 13/13" which is the one sub-directory in my monorepo I had actually pushed new code to.

My feature request:

• When syncing Railway projects deployed from GitHub monorepo templates, discern which services build from the code that was pushed. Respect the "root directory" configured on the services, and only offer the option to redeploy when it is relevant.

• When opening the "Sync Project" modal, list every service that has had updates on the upstream template.

• Offer the option to redeploy each of them separately and all at once, without closing the modal.