GET commits patch got 404 error #14400

Closed
opened 2025-11-02 11:11:58 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @hoffmannlin on GitHub (Apr 23, 2025).

Image

Description

GET /repos/{owner}/{repo}/git/commits/{sha}.{diffType}

Got 404 | Error: Not Found

Image

Gitea Version

1.23.7

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

use docker

Database

MySQL/MariaDB

Originally created by @hoffmannlin on GitHub (Apr 23, 2025). ![Image](https://github.com/user-attachments/assets/d90ad989-c885-4a2f-a556-98443a86684d) ### Description GET /repos/{owner}/{repo}/git/commits/{sha}.{diffType} Got 404 | Error: Not Found ![Image](https://github.com/user-attachments/assets/b94359a7-0b4b-4ac8-8bad-13f6ddbb1113) ### Gitea Version 1.23.7 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? use docker ### Database MySQL/MariaDB
GiteaMirror added the issue/needs-feedback label 2025-11-02 11:11:58 -06:00
Author
Owner

@wxiaoguang commented on GitHub (Apr 23, 2025):

It works (Hmm, I have tested, but GitHub has some 500 errors and I can't upload my screenshot at the moment. Update: see next comment)

If you see 404, maybe that "commit id" doesn't exist in your repo.

@wxiaoguang commented on GitHub (Apr 23, 2025): It works (Hmm, I have tested, but GitHub has some 500 errors and I can't upload my screenshot at the moment. Update: see next comment) If you see 404, maybe that "commit id" doesn't exist in your repo.
Author
Owner

@wxiaoguang commented on GitHub (Apr 23, 2025):

Image

@wxiaoguang commented on GitHub (Apr 23, 2025): ![Image](https://github.com/user-attachments/assets/9153209a-1e8f-41e1-a5a7-a375a772f086)
Author
Owner

@hoffmannlin commented on GitHub (Apr 23, 2025):

Sorry, that was my mistake. I accidentally pushed code from repo b to repo a for review, but the feature itself is functioning properly without any issues.

@hoffmannlin commented on GitHub (Apr 23, 2025): Sorry, that was my mistake. I accidentally pushed code from repo b to repo a for review, but the feature itself is functioning properly without any issues.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14400