2 months ago
From what I can tell, the only way to specify a branch that a GitHub repo connected service should use is to use the "branch connected to production" setting.
However this also then enables the automatic deploy whenever something is to pushed to the branch, which I don't want.
Is there any way to specify that the repo should use the "release/deploy" branch without also automatically starting a new deployment when a change is pushed?
5 Replies
2 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
2 months ago
This is just a theory but try adding !/* to your watch path, this will hopefully tell Railway to ignore all changes. I'm completely unsure whether this will work or not maybe it's my best guess for this
dev
This is just a theory but try adding !/* to your watch path, this will hopefully tell Railway to ignore all changes. I'm completely unsure whether this will work or not maybe it's my best guess for this
2 months ago
or actually upon reading the docs, if that doesn't work try doing this instead:
/package.json
!/*from what I can gather negations like !/* will only work if some files are included in a preceding rule. In this case we add package.json but that's just an example, try adding whatever file in there that you probably wont change, maybe point it to some static file that you just never change. Once again, completely unsure if this will work or not, but it's the only thing I can think of other than what uxuz said
uxuz
Ignore this message, try out what is mentioned above.
2 months ago
sorry uxuz!!!!! 
it's not on purpose i swear