I have wasted an unnecessary amount of time trying to deploy a private Github repository (from an org account). It eventually worked, but the steps to get there are not documented and surely could have been better.

These are roughly my steps:

1. Sign up as a new account

2. Try to deploy using a Github URL

3. Get hit with the message "Only public repositories can be added using the GitHub URL."

4. Start to wonder why that would be the case, as surely Railway would allow deploying non-public repositories. Do I need to upgrade my plan? Are permissions bad? Based on the wording, it seemed the URL was the issue – spend a bunch of time to find other ways to deploy Github repos.

5. Eventually give up on that, then find the ability to manage the Github auth settings, which allows me to grant permission to private org repos.

6. Happy that private repo access has been granted, attempt to deploy the service again.

7. ONCE AGAIN hit with the error message "Only public repositories can be added using the GitHub URL.", only in a different way this time. Spend time checking the support forums to see if others are experiencing this.

8. Reload the page – it seems to work but says it cannot deploy it.

9. Reload the page a couple more times, suddenly works.

Happy to say that I got it working in the end, but the way to get here was messy. Surely this can be improved, or at the very least documented a bit better. There also might be some cache that needs to be invalidated, as indicated by steps 7-9.