-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
404 Response after successfully applying patch from diff file #22621
Comments
I reproduced this bug
|
This was referenced Feb 22, 2023
jolheiser
pushed a commit
that referenced
this issue
Feb 23, 2023
yardenshoham
pushed a commit
to yardenshoham/gitea
that referenced
this issue
Feb 23, 2023
lunny
pushed a commit
that referenced
this issue
Feb 24, 2023
Backport #23086 Fixes #22621 (comment) Co-authored-by: yp05327 <[email protected]>
I don't think this issue can be closed, as the main fix PR is #23056 which is not closed. |
zeripath
pushed a commit
that referenced
this issue
Feb 24, 2023
yardenshoham
pushed a commit
to yardenshoham/gitea
that referenced
this issue
Feb 24, 2023
zeripath
pushed a commit
to zeripath/gitea
that referenced
this issue
Feb 24, 2023
…ix commit name in Apply Patch page (go-gitea#23086) Backport go-gitea#23056 Backport go-gitea#23086 Fixes go-gitea#22621 Fixes go-gitea#22621 (comment)
techknowlogick
pushed a commit
that referenced
this issue
Feb 25, 2023
Backport #23056 Fixes #22621 Co-authored-by: yp05327 <[email protected]>
lunny
pushed a commit
that referenced
this issue
Mar 15, 2023
…t name in Apply Patch page (#23086) (#23131) Backport #23056 Backport #23086 Fixes #22621 Fixes #22621 (comment) Co-authored-by: yp05327 <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
When applying a patch (via code tab -> Add File -> Apply Patch) the patch is applied correctly, but the server responds with a 404. The after creating the patch commit the redirect that 404s is for USER/REPOSITORY/branch/main/diff.patch, which does not exist of course.
I could reproduce it here:
https://try.gitea.io/pahofmann/patch-404-test/
After I applied the patch I was redirected to https://try.gitea.io/pahofmann/patch-404-test/src/branch/main/diff.patch
Gitea Version
1.18.1
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
https://gist.github.com/pahofmann/fb2c2e9daa8ff8d2c846b85e1eca3598
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Fresh setup in container.
Database
SQLite
The text was updated successfully, but these errors were encountered: