2 years ago
When an App opens a PR (e.g. dependabot) Railway declines to create a PR Environment with the error message:
This PR was not deployed automatically as @[bot] does not have access to the Railway project.
In order to get automatic PR deploys, please add @[bot] to the project inside the project settings page.Unfortunately, it's impossible to add a bot, as their email is a no-reply email associated with github.com. +bot_name@users.noreply.github.com is the format.
My sense is that Railway should basically allow PR deploys from bots if it's enabled on the repo perhaps by checking the emails associated with the commits. Alternatively, Railway could allow adding "bot emails" to a project, and treat those as already accepted/invited users.
4 Replies
2 years ago
Anyone have a workaround in interim? I've tried creating a new account w/ a different email and changing the email for example, but no luck.
2 years ago
+1 Would be great if Railway would support known bots
2 years ago
We've added support for Dependabot and Renovate Bot: https://docs.railway.app/guides/environments#bot-pr-environments
2 years ago
@david that is awesome!
Any chance could also add support for custom bot names? or just any username that ends in [bot] or email that follows the format above.
Our product is literally a Github Bot that pushes PRs, so would be amazing to test those PRs out in a preview env before merging.