16 days ago
If a PR is opened from the main repo itself, our project repo can create the PR Environment normally. However, if the PR is created from a forked repo to the main repo, the PR Environment cannot be created. Please see attached images.
All relevant members have confirmed that they have already joined the workspace and have the required permissions.
Could you please help investigate the cause? Thank you.
Attachments
4 Replies
16 days ago
Your workspace is active on Pro with 6 members, and the configuration appears correct. PR environments currently require the PR to originate from a branch on the same repository that is connected to the service. PRs from forked repositories do not trigger PR environment creation, even when the fork author is a workspace member. This is a known platform limitation. As a workaround, contributors can push their branches directly to the main repository instead of opening PRs from forks.
Status changed to Awaiting User Response Railway • 16 days ago
16 days ago
Is there any plan to support forked PR in the future?
Maybe add a process to ask maintainers to allow the building?
Or add an options that allows fully private repo can has no limit?
This will be very helpful for a medium to large company to build the review flow.
Status changed to Awaiting Railway Response Railway • 16 days ago
15 days ago
That sounds like a feature request! Can you write up a detailed explanation of your use case and the feature? This way other users can upvote your issue and glob onto it.
You can write your feature request and view the roadmap here ---> https://station.railway.com/roadmap
Status changed to Awaiting User Response Railway • 15 days ago
14 days ago
Thank you, I post a new feature request there.
Status changed to Awaiting Railway Response Railway • 14 days ago
Status changed to Solved asika32764 • 14 days ago