Mike
GitHub deployment trigger doesn't fire for "success"
I'm working on a GitHub workflow that runs e2e tests against a preview deployment that is automatically created & updated by Railway.
I want to leverage the
deployment_status GitHub workflow trigger and further narrow it down to the success type. In other words, only trigger that workflow when Railway successfully deployed a new deployment.
The issue I have is that for some reason my workflow gets triggered twice with action: "created", once when the deployment starts and once when it finishes. The second one should be a action: "success".
Can anyone confirm that or is it a user error on my side?
I'll post a sample workflow yaml in the thread.6 replies
DB Migration replaced DATABASE_URL with DATABASE_PRIVATE_URL
Hi 👋, I used the one-click DB migration and noticed that the
DATABASE_URL env variable in Vercel disappeared and was replaced by a DATABASE_PRIVATE_URL.
I can manually add the DATABASE_URL back, but want to confirm that's ok to make sure I don't interfere with the Railway <> Vercel integration.33 replies