-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Create Pull Request in Forked Repo #26193
Comments
Can you give me detailed steps to reproduce this bug? |
Sure! So on my instance I have the following repo mirrored: Then fork that repo to your personal user as the owner. Try to create a new Pull Request on your forked repo and (for me at least) the pull into and pull from will both be only your personal forked repo with no ability to change the pull from to be that mirrored repo (which I've been able to do in the past and is a necessary action). |
Okay, so now fork that mirror you created. On that fork try to create a PR to pull in changes from the local mirror, the only option you should see on the pull from dropdown is the fork itself making the PR unusable. |
I'm sorry I still can't reproduce the problem you're talking about, are you able to provide a video showing the problem you're talking about? |
I can see about a video potentially, never had to make one so I will have to get something to do that. But in the meantime here's a step-by-step that hopefully allows you to reproduce the problem:
|
Possible duplicate of #24585 |
I think the issue here is that we're unable to create a pull request from the mirror repo, less so to the mirror repo. |
This! We used to be able to, according to the linked issue above it appears this broke in a dot fix for 1.19 (I haven't done it for a while). |
it broke when i updated to latest gitea, please fix |
…ource. (#26785) ## Description Sometimes, we need to use an upstream mirror repository to update the current development repository, but mirror repositories are prohibited from PR. It should not appear in `merge to,` but it can appear in `pull from.` Fix #24585 #26193 #26781 Related #24183 Many thanks to @apnote for assisting me in reproducing this bug! ## ScreenShot --- ### Before <img src="https://github.com/go-gitea/gitea/assets/50507092/3d76c376-1f54-45b9-80c9-6ba8319d6a9a" width="400px"> <img src="https://github.com/go-gitea/gitea/assets/50507092/fbfd9f7f-421f-4a2e-9a3e-f2958bbf3312" width="400px"> ### After <img src="https://github.com/go-gitea/gitea/assets/50507092/e6984524-4f61-4310-b795-4d8598bd8963" width="400px"> <img src="https://github.com/go-gitea/gitea/assets/50507092/04065b44-78d7-4721-bf31-0f1674150727" width="400px">
…ource. (go-gitea#26785) ## Description Sometimes, we need to use an upstream mirror repository to update the current development repository, but mirror repositories are prohibited from PR. It should not appear in `merge to,` but it can appear in `pull from.` Fix go-gitea#24585 go-gitea#26193 go-gitea#26781 Related go-gitea#24183 Many thanks to @apnote for assisting me in reproducing this bug! ## ScreenShot --- ### Before <img src="https://github.com/go-gitea/gitea/assets/50507092/3d76c376-1f54-45b9-80c9-6ba8319d6a9a" width="400px"> <img src="https://github.com/go-gitea/gitea/assets/50507092/fbfd9f7f-421f-4a2e-9a3e-f2958bbf3312" width="400px"> ### After <img src="https://github.com/go-gitea/gitea/assets/50507092/e6984524-4f61-4310-b795-4d8598bd8963" width="400px"> <img src="https://github.com/go-gitea/gitea/assets/50507092/04065b44-78d7-4721-bf31-0f1674150727" width="400px">
Fixed by #26785 |
…ource. (#26785) (#26790) Backport #26785 by @CaiCandong ## Description Sometimes, we need to use an upstream mirror repository to update the current development repository, but mirror repositories are prohibited from PR. It should not appear in `merge to,` but it can appear in `pull from.` Fix #24585 #26193 #26781 Related #24183 Many thanks to @apnote for assisting me in reproducing this bug! ## ScreenShot --- ### Before <img src="https://github.com/go-gitea/gitea/assets/50507092/3d76c376-1f54-45b9-80c9-6ba8319d6a9a" width="400px"> <img src="https://github.com/go-gitea/gitea/assets/50507092/fbfd9f7f-421f-4a2e-9a3e-f2958bbf3312" width="400px"> ### After <img src="https://github.com/go-gitea/gitea/assets/50507092/e6984524-4f61-4310-b795-4d8598bd8963" width="400px"> <img src="https://github.com/go-gitea/gitea/assets/50507092/04065b44-78d7-4721-bf31-0f1674150727" width="400px"> Co-authored-by: CaiCandong <50507092+CaiCandong@users.noreply.github.com>
Description
Unable to test this on the demo site since you can't create orgs on it.
I have an organization on my Gitea (Bitwarden) which as the server repo which is a mirror of the repo on GitHub. I have forked that repo to my user and that's where I create modified branches and things to test with. Before I go to create a new modified branch I create a new pull request to pull changes in from the mirror to my fork... With 1.20.1 this is broken and only lets me pull changes from the repo into itself (and doesn't let me choose the source repo that the repo was forked from).
Gitea Version
1.20.1
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
Git Version
2.40.1
Operating System
Ubuntu 18.04.6 LTS
How are you running Gitea?
Binary download from release ran as a service with systemd.
Database
MySQL
The text was updated successfully, but these errors were encountered: