Make sure the Railway GitHub App has access to your new repositories by going to your GitHub Apps settings, clicking Configure next to Railway, and adding the repos under "Repository access." After that, click Add -> GitHub Repository -> Refresh in your project canvas to force a cache refresh.

I have already did that still the repo is not populating

We see your repositories aren't populating even after granting access and refreshing. This is a known sync issue on our side where the repository list can get stuck on a stale cache, not anything wrong with your setup. We're getting it refreshed on our end and will follow up here; once it's done, reload the project and try Add, then GitHub Repository again.

please let me know once you have resolved the issue,we need to deploy two of our projects

Hii ,I still see the issue,can you please provide any ETA on this?

Thanks for your patience, and sorry for the wait. We've refreshed the GitHub installation cache for your account on our end. Please reload project cvedits, then click Add -> GitHub Repository -> Refresh.

One thing we want to flag so this resolves cleanly: after the refresh, our side currently sees only one repository granted to the Railway GitHub App on your account (rugvailabs): rugvailabs/rugvai-labs. If the repos you're trying to deploy aren't appearing, it's almost always one of these two things:

1. The repo hasn't actually been added to the Railway App's allowed list yet. Go to https://github.com/settings/installations, click Configure next to Railway, and under "Repository access" confirm each repo you want is listed (or switch to "All repositories"). If you just changed this, click Save.

2. The repo lives under a different GitHub account or organization than rugvailabs. The Railway App is installed per account/org, so a repo owned by another org needs the App installed and granted there too.

Once the repo shows under "Repository access" for the right owner, reload cvedits and hit Add -> GitHub Repository -> Refresh again and it should populate. If it's still missing after that, reply with the exact repo name (owner/repo) and we'll dig in right away.