Feature Request: Expose Git Blame Functionality via API #14333

New Issue

GiteaMirror · 2025-11-02T11:10:05-06:00

GiteaMirror commented

2025-11-02 11:10:05 -06:00

Originally created by @GuangYiDing on GitHub (Apr 3, 2025).

Originally assigned to: @adlternative on GitHub.

Feature Description

Title: Feature Request: Expose Git Blame Functionality via API

Description:
I would like to request the exposure of git blame functionality through Gitea's API. Currently, while Gitea provides comprehensive API endpoints for various Git operations, there appears to be no dedicated endpoint for retrieving git blame information programmatically.

Problem Statement:
Many modern development tools and integrations rely on blame data for features such as:
• Code authorship attribution
• Historical context for code reviews
• Integration with analytics/metrics platforms
• Traceability in debugging workflows

Platforms like GitHub, GitLab, and Gitee already provide native support for git blame through their APIs (GitHub example, GitLab example). Even indirect implementations (like Gitee's combination of file content and commit history APIs) offer workarounds. Gitea currently lacks this capability, forcing developers to implement local blame calculations or maintain alternative solutions.

Thank you for considering this request. I believe this addition would bring Gitea closer to parity with other major Git platforms while maintaining its lightweight advantages.

Screenshots

No response

Originally created by @GuangYiDing on GitHub (Apr 3, 2025). Originally assigned to: @adlternative on GitHub. ### Feature Description **Title:** Feature Request: Expose Git Blame Functionality via API **Description:** I would like to request the exposure of git blame functionality through Gitea's API. Currently, while Gitea provides comprehensive API endpoints for various Git operations, there appears to be no dedicated endpoint for retrieving git blame information programmatically. **Problem Statement:** Many modern development tools and integrations rely on blame data for features such as: • Code authorship attribution • Historical context for code reviews • Integration with analytics/metrics platforms • Traceability in debugging workflows Platforms like GitHub, GitLab, and Gitee already provide native support for git blame through their APIs ([GitHub example](https://docs.github.com/en/graphql/reference/objects#blame), [GitLab example](https://docs.gitlab.com/user/project/repository/files/git_blame/)). Even indirect implementations (like Gitee's combination of file content and commit history APIs) offer workarounds. Gitea currently lacks this capability, forcing developers to implement local blame calculations or maintain alternative solutions. Thank you for considering this request. I believe this addition would bring Gitea closer to parity with other major Git platforms while maintaining its lightweight advantages. ### Screenshots _No response_

GiteaMirror added the topic/api type/proposal labels 2025-11-02 11:10:05 -06:00

GiteaMirror commented

2025-11-02 11:10:06 -06:00

@adlternative commented on GitHub (Apr 6, 2025):

This sounds easy to do. I'm willing to support this later.

@adlternative commented on GitHub (Apr 6, 2025): This sounds easy to do. I'm willing to support this later.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#14333