Add option to blame files

[andrzejressel]

Introduces option to blame text files.

closes #747

Regarding https://github.com/go-gitea/gitea/pull/5721/files#diff-4c18d74f0d0687b8503915779673f3ebR393 - width was set to 1%, but it seems to scale anyway.

[codecov-io]

Codecov Report

Merging #5721 into master will decrease coverage by 0.07%.
The diff coverage is 22.6%.

@@            Coverage Diff            @@
##           master   #5721      +/-   ##
=========================================
- Coverage   40.87%   40.8%   -0.08%     
=========================================
  Files         416     418       +2     
  Lines       57013   57274     +261     
=========================================
+ Hits        23303   23368      +65     
- Misses      30589   30783     +194     
- Partials     3121    3123       +2

Impacted Files	Coverage Δ
routers/repo/blame.go	0% <0%> (ø)
routers/routes/routes.go	82.29% <100%> (+0.11%)	⬆️
models/git_blame.go	78.26% <78.26%> (ø)
models/gpg_key.go	54.72% <0%> (+0.83%)	⬆️
modules/log/event.go	65.98% <0%> (+1.52%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b9d1fb6...3a57b9c. Read the comment docs.

[lafriks]

Even though I don't like current approach of git methods being in different repository but to be consistent git operations should be moved to go-gitea/git probably

[zeripath]

Heya! Thanks for your first PR. It's a good idea to add this functionality, but see my comments.

[jonasfranz]

Do you consider adding screenshots to this PR?

[andrzejressel]

@jonasfranz Done

[silverwind]

Screenshot feedback:

1. The black lines introduce too much contrast, I'd try #888 or similar.
2. The right side of the file header looks weird. Try to get the content on 1 line and add some margins, especially to the right side of the buttons.

[MarkusAmshove]

Does this work 'recursive, e.g. clicking on a commit on the left side opens a blame of this file with the context of the commit?

[stale]

This pull request 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 months. Thank you for your contributions.

[tonivj5]

Any news?

[lafriks]

Resolved conflicts and updated UI

[lafriks]

Added author icons:

[lafriks]

@lunny @zeripath please review

[MarkusAmshove]

Do the links in the blame view go to the commit (e.g. show an overview of that particular commit) or to the same file in the clicked commit, opening the blame view again?
The latter one would be really helpful (maybe with an extra button), because it makes it easier to actually blame across multiple commits

[zeripath]

OK this is still rendering the whole blame in memory but I guess we can probably fix this later and get it more efficient once it's in.

[lunny]

unnecessary blank line.

[lunny]

@lafriks I think we also need commit time with the author?

[silverwind]

Few ideas:

• Make the blame column font non-monospaced.
• Make the blame column a bit wider to let more of the message show.
• Add relative commit date in the blame column or tooltip.
• Add user-select: none to the blame column to allow copying only code.

[lafriks]

Fixed conflicts, added commit time and made blame info not selectable:

[lafriks]

@lunny please review

[lunny]

@jereksel @lafriks good work. If you can move git parts to modules/git, that's better. I will not block this PR, but since git module merged to main repository. That maybe not difficult.

[6543]

there is a bounty for this PR: https://www.bountysource.com/issues/41291710-feautre-request-git-blame