Currently, when our GitHub workflow attempts to trigger a deployment to our Railway project (ebaloaloa/eventvault), we encounter permission issues if the deploying entity isn't a recognized named user or a specifically supported bot like dependabot. We recently saw an error message: "This PR was not deployed automatically as @copilot does not have access to the Railway project. In order to get automatic PR deploys, please add @copilot to your team on Railway."

While I understand that @copilot itself might not be a direct integration Railway supports by that name, this highlights a need for a more flexible way to grant deployment permissions to general GitHub-based deployment triggers, such as those initiated by GitHub Actions or other CI/CD tools that might be represented by a generic service principal or GitHub App.