Feautre Request: Git Blame #277

Closed
opened 2025-11-02 03:17:01 -06:00 by GiteaMirror · 20 comments
Owner

Originally created by @plessbd on GitHub (Jan 24, 2017).

Github gives us to look at a blame page for a file:
image
resulting in something like: https://github.com/go-gitea/gitea/blame/master/CONTRIBUTING.md

It would be nice to have this feature in Gitea as well.

this is a duplicate of gogits/gogs#2606


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Originally created by @plessbd on GitHub (Jan 24, 2017). Github gives us to look at a blame page for a file: ![image](https://cloud.githubusercontent.com/assets/683012/22263094/3cf75d3a-e241-11e6-8a74-d110b54e9cd0.png) resulting in something like: https://github.com/go-gitea/gitea/blame/master/CONTRIBUTING.md It would be nice to have this feature in Gitea as well. this is a duplicate of gogits/gogs#2606 <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/41291710-feautre-request-git-blame?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>
GiteaMirror added the type/featureissue/confirmed labels 2025-11-02 03:17:01 -06:00
Author
Owner

@makhov commented on GitHub (Jan 24, 2017):

Good idea. I'll try to make the feature.
@tboerger assign it to me, please

@makhov commented on GitHub (Jan 24, 2017): Good idea. I'll try to make the feature. @tboerger assign it to me, please
Author
Owner

@tboerger commented on GitHub (Feb 10, 2017):

Solved via #32

@tboerger commented on GitHub (Feb 10, 2017): Solved via #32
Author
Owner

@plessbd commented on GitHub (Feb 10, 2017):

I do not believe this is solved by #32 or go-gitea/git#32
I believe that @makhov is still working on it in his feature branch https://github.com/makhov/gitea/tree/feature/blame

@plessbd commented on GitHub (Feb 10, 2017): I do not believe this is solved by #32 or go-gitea/git#32 I believe that @makhov is still working on it in his feature branch https://github.com/makhov/gitea/tree/feature/blame
Author
Owner

@tboerger commented on GitHub (Feb 10, 2017):

You are right, properly checking the references helps :)

@tboerger commented on GitHub (Feb 10, 2017): You are right, properly checking the references helps :)
Author
Owner

@lunny commented on GitHub (Mar 3, 2017):

It seems git blame have to be used in a git workspace?

@lunny commented on GitHub (Mar 3, 2017): It seems `git blame` have to be used in a git workspace?
Author
Owner

@strk commented on GitHub (Mar 11, 2017):

@makhov any news on this ?
This feature was considered in the Git hosting solution comparison table of notabug.org:
https://ethercalc.org/choose-the-git-host.html

@strk commented on GitHub (Mar 11, 2017): @makhov any news on this ? This feature was considered in the Git hosting solution comparison table of notabug.org: https://ethercalc.org/choose-the-git-host.html
Author
Owner

@plessbd commented on GitHub (Apr 19, 2017):

@makhov any news? Would love t see this feature.

@plessbd commented on GitHub (Apr 19, 2017): @makhov any news? Would love t see this feature.
Author
Owner

@plessbd commented on GitHub (May 30, 2017):

Any progress on this?

@plessbd commented on GitHub (May 30, 2017): Any progress on this?
Author
Owner

@lunny commented on GitHub (May 31, 2017):

@plessbd nobody on this issue now I think.

@lunny commented on GitHub (May 31, 2017): @plessbd nobody on this issue now I think.
Author
Owner

@bkcsoft commented on GitHub (Jun 1, 2017):

Unassigned for lack of status :)

@bkcsoft commented on GitHub (Jun 1, 2017): Unassigned for lack of status :)
Author
Owner

@lcges commented on GitHub (Aug 31, 2017):

Who is working on this?

@lcges commented on GitHub (Aug 31, 2017): Who is working on this?
Author
Owner

@ptman commented on GitHub (Aug 31, 2017):

Assignees seems pretty empty to me

@ptman commented on GitHub (Aug 31, 2017): Assignees seems pretty empty to me
Author
Owner

@lcges commented on GitHub (Aug 31, 2017):

If I understand well?
The issue is up to you - but you have not done anything yet?

@lcges commented on GitHub (Aug 31, 2017): If I understand well? The issue is up to you - but you have not done anything yet?
Author
Owner

@dj-thd commented on GitHub (Mar 16, 2018):

Any news? I would love to see that feature but unfortunately I'm not proficient with Go :(

@dj-thd commented on GitHub (Mar 16, 2018): Any news? I would love to see that feature but unfortunately I'm not proficient with Go :(
Author
Owner

@cdstg commented on GitHub (Nov 16, 2018):

I also want lol

@cdstg commented on GitHub (Nov 16, 2018): I also want lol
Author
Owner

@stale[bot] commented on GitHub (Jan 15, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 15, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Author
Owner

@ptman commented on GitHub (Jan 15, 2019):

there's a fresh pull request, how is this stale?

@ptman commented on GitHub (Jan 15, 2019): there's a fresh pull request, how is this stale?
Author
Owner

@techknowlogick commented on GitHub (Jan 15, 2019):

@ptman stalebot doesn’t know about linked PRs. This is something we are looking into updating

@techknowlogick commented on GitHub (Jan 15, 2019): @ptman stalebot doesn’t know about linked PRs. This is something we are looking into updating
Author
Owner

@stale[bot] commented on GitHub (Mar 16, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 16, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Author
Owner

@NotAFile commented on GitHub (Mar 16, 2019):

still an open pr

@NotAFile commented on GitHub (Mar 16, 2019): still an open pr
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#277