a year ago
Hi, I have a private repo(nextjs app) and I created a template using that repo. I have shared that template with someone and that person also has access to the repo (added as a collaborator).
Now, whenever I push a change to my private repo...
The latest changes are not being auto deployed for that person. Even though the source repo is pointing to my private repo and connected to same branch.
Even after clicking on "Disconnect" and then reconnecting, it's still picking and deploying old commits.
19 Replies
a year ago
Hello,
You would need to disconnect the template's source repo, click Deploy, connect the desired repo, click Deploy.
This will allow the other person's service to auto-deploy on push.
These steps have likely not been performed correctly, so I highly recommend starting over with a fresh template deployment.
Best,
Brody
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
This is how current setup looks for anyone who sets up project using my template. Is this correct?
Because, whenever I push something to prod branch, nothing happens.
Also, When I click "check for updates", it always says "You're on the latest version of this repository"- This is wrong.
Attachments
Status changed to Awaiting Railway Response Railway • about 1 year ago
Status changed to Awaiting User Response Railway • about 1 year ago
brody
Hello,Please follow the steps I have given in my first message.
a year ago
I have tried both methods:
Did as you suggested
Forked the source repo and connected it. On syncing changes from source repo, I expect an auto deployment.
In both cases, unfortunately the changes are not auto deploying.
Btw, what’s “desired” repo? In my case, It’s the same repo I want to connect to.
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Can you please link to the service that you have completed the steps I have provided on? even if its the other user's service.
desired = the same repo you want to connect to.
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
I’m sorry, I didn’t understand the first part of your message.
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Please share a link to the service that you have completed the given steps on.
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
You have not completed the four steps outlined in my first message, please go ahead and do that at your earliest convenience.
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
I just now completed these steps again, disconnected the source repo -> Deploy (It did nothing) -> connected back same repo -> Deploy.
But if you can see, It again pulled an old commit. Please refer to the commits history screenshot I've shared below.
Attachments
Status changed to Awaiting Railway Response Railway • about 1 year ago
manojnaidu619
I just now completed these steps again, disconnected the source repo -> Deploy (It did nothing) -> connected back same repo -> Deploy.But if you can see, It again pulled an old commit. Please refer to the commits history screenshot I've shared below.
a year ago
To give you context around my situation:
I have a Nextjs app which is on GitHub as a private repo.
I have created a template using this private repo and I have shared this template with my clients so that they can deploy themselves with one click. Until here everything works fine.
Problem is when I push an update to my source repo. I want to make sure that my client’s service is also auto deployed. But currently it’s not happening.
I have tested these two methods(for clients). In both cases, auto deployment is not being triggered on pushing update.
Client’s project created with the template directly points to source repo
Client’s project created with the template points to forked repo of the source repo
Note that, client has access to my repo(added as a collaborator)
So, ultimate goal is to auto deploy my client’s project on source repo update.
I have even tried as you suggested, but no success.
Please let me know if I’m doing anything wrong or any other ways to solve my issue. Thanks
a year ago
Hello,
Looks like you have followed the steps, you can now deploy the latest commit with ctrl / cmd + k -> deploy latest commit and I have done that for you to show that it works.
Best,
Brody
Status changed to Awaiting User Response Railway • about 1 year ago
brody
Hello,Looks like you have followed the steps, you can now deploy the latest commit with ctrl / cmd + k -> deploy latest commit and I have done that for you to show that it works.Best,Brody
a year ago
Thanks, But why is it that it's not auto deploying? or show me that message "A new update is available" that I usually see on the left panel in my project.
Status changed to Awaiting Railway Response Railway • about 1 year ago
Status changed to Awaiting User Response Railway • about 1 year ago
brody
I'm not sure, I'll have to attempt to reproduce it
a year ago
Sure, please help me out here.
Atleast now that I know how to manually trigger deployment with latest commit, I'll continue with my work.
I'll be waiting for your message :)
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
For the sake of transparency this is likely not something we will be able to prioritize a fix for any time soon, even if I'm able to reproduce.
Status changed to Awaiting User Response Railway • about 1 year ago
brody
For the sake of transparency this is likely not something we will be able to prioritize a fix for any time soon, even if I'm able to reproduce.
a year ago
Ok, I appreciate that.
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
I'll still ticket, but to bump this in priority would require several more reports of this affecting users.
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
An internal ticket has been attached to this thread. Updates will be relayed in this thread, so keep an eye out!
Status changed to Solved Railway • about 1 year ago
6 months ago
❌ The ticket "Update button not detecting new changes" has been marked as canceled.