Railway not seeing updates to upstream (public) repository
I am connected to a public GitHub repo. When first connected, it properly deploys as expected.
However, the repo recently had a pull request merged to main, and yet when I go in Railway settings and click 'Check for Updates' it says 'You're on the latest version of this repository'. So this means I'm effectively stuck on the previous version of the repo.
I originally connected it using CMD+K to paste the public GitHub repo link, and it connected well this way. To make matters stranger, the first PR that was merged to main after that was seen by Railway when I checked for updates, so I was able to get those updates, but nothing since.
Am I doing something wrong? Is there something further to do to ensure that you get updates when connected to a public upstream repo?
10 Replies
Project ID:
N/APerhaps of note, the latest PR only changes the
/nixpacks.toml file in the public repo. Maybe this didn't meet a threshold for changes? My 'Root directory' is the default / though so I don't really see this being the issue. In fact my whole project uses default settings except the start command and having environment variables.
project ID: a9d9c589-b108-418d-951e-f5817ea3bc1fFurther, when I click 'Connect Environment to Branch' under Git Repository, I get the attached error. It's definitely connected though as under 'Source Repo' and 'Linked to Upstream repo' (see my OP) it properly shows the repo connected, and when you click that you go to the public repo's location, where you can see the changes that Railway is missing. I'm guessing this is for actually connecting to your own repo, which is not what I'm doing.
hiding the repo is not doing you any favours 😆
It's just a regular old public repo, I'll ping it to you.
what does ping it to me mean
DM, just sent.
I'm actually wondering if this is the problem. I noted that in railway the 'default' for watch paths appears to be
src/**, which would by definition ignore the main folder where the nixpacks config file is...
I'm going to experiment by changing this to ** and see if it then picks up the next change to the repo.
#🛂｜readme #5
thats not a default, thats a placeholder https://www.w3schools.com/tags/att_input_placeholder.asp
Ok well then not sure what else could cause it.