We can confirm the GitHub deployment status for PR environments is linking to the project settings page instead of the actual preview URL (e.g., web-cal-com-pr-6.up.railway.app). We've filed this as a bug for our engineering team to address.

This is actually intended behaviour because we create a single GitHub deployment per Railway PR environment. This means there can be multiple services with URLs and there is no clear URL that we can surface. What would your tool expect in this case (e.g. you have a Railway environment with 5 services that all have different web URLs)?

Our tool do E2E test against the deployed URL in a PR: We listen the deployment event from Github Webhook and use the deploymentStatus?.environment_url || deployment?.payload?.web_url as the targeted testing URL. By this logic, we integrated finely with Vercel and Render.

Since Railway is doing a deployment, and I guess it should expose the deployed URL in Github event, so others tools can refer to it.

Maybe you can let me know where is the preview URL stored in payload in in your case, so we can do better integration.

Currently the preview URL isn't exposed anywhere in the GitHub deployment status payload. As mentioned, we create one GitHub deployment per PR environment, which can contain multiple services with different URLs, so we link to the project page instead. We've tracked this as a feature request for our engineering team to explore, potentially surfacing service URLs when there's only a single service with a domain in the environment.