-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Pull request creation to forked repository via web api fails #20475
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
Comments
fix go-gitea#20475 Signed-off-by: a1012112796 <[email protected]>
Since #26785, it become able to create PR to forked repository from origin via web. I've tested with try.gitea.io using this repository.
On the my instance running 1.20.4 also have same issue.
By the way, I know #20479 is closed recently. Is there any plan with this ..? |
I'm also running into the exaqct issue on v1.22.1 |
Resolves #20475 Backport #31863 Co-authored-by: Job <[email protected]>
Resolves go-gitea#20475 (cherry picked from commit 7e68bc8) Conflicts: tests/integration/pull_create_test.go add missing testPullCreateDirectly from c63060b Fix code owners will not be mentioned when a pull request comes from a forked repository (go-gitea#30476)
Description
Gitea prevents pull request creation with the web api from the original repository to the fork with the error message:
<Response [404]> b'{"errors":null,"message":"GetForkedRepo","url":"https://try.gitea.io/api/swagger"}\n'
.I managed to reproduce the issue on https://try.gitea.io/Lixfel/FreeSql .
Reproduction code:
Bug origin assumption:
https://github.com/go-gitea/gitea/blob/main/routers/api/v1/repo/pull.go#L967 seems to only allow PRs from the fork to the original repository, a method call
GetForkingRepo
is missing.Gitea Version
1.16.9
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
https://gist.github.com/lixfel/e0c36e3b85a1b8ffbf994baf275e49bd
Screenshots
No response
Git Version
1:2.30.2-1 (apt version)
Operating System
Debian
How are you running Gitea?
Use of Gitea Downloads site; execution with systemd
Database
MySQL
The text was updated successfully, but these errors were encountered: