Can you make sure you have given the Railway App bot access to your repositories?

GitHub Settings -> Applications -> Railway App -> Configure -> Repository access

Then please go into your Railway account and unlink and relink the GitHub integration.

Thank you, I did this before.... I am trying again with no success...

My GitHub config:

Permissions

• Read access to metadata
• Read and write access to actions, administration, checks, code, commit statuses, deployments, pull requests, and workflows

Repository access

• All repositories

The repository is private but that shouldn't be a problem.

Just in case, I want to explain something strange that I did that could have maybe intefered: when I first created my user account I selected my GitHub profile. Very soon I realized that an old email address was kept as email in the Railway account, so I changed it (I think before any attempt of deploying from GitHub).

Could have this triggered a problem? I have tried now to remove this old email address from the GitHub account but that didn't made a difference.

Your Hobby subscription and GitHub permissions both look correct on our end. Since reconfiguring the Railway App in GitHub has not resolved this, the next step is to fully uninstall the Railway GitHub App from your GitHub account (GitHub Settings > Applications > Railway App > the gear icon > Uninstall), then reinstall it from this link, granting access to your repositories. After that, go to your Railway account settings and relink the GitHub integration.

I had done it in the past....

I finally found the way to make it work:

Instead of using the link "Deploy the repo XXXX" (below "There is no active deployment for this service."), i used the general pink "Deploy" button....

....This bug made me lose a lot of time