Feature Description

Consider the scenario where a given file has 1+ change in its commit history, then the file is renamed using git mv or so, and then the file receives another change.

In the command line git, you can get the log changes before renaming the file using --follow.

When viewing the same history in the Web UI, the history of that file ends where the file was last renamed. Giving the false impression of history lost.

A simple button/check to activate the --follow option would be much appreciated. In fact, I'd say this should be enabled by default.

To see it, given a file that was renamed, check its history in the web UI and then compare it with the following:

As Gitea does:

git log FILE

As Gitea should do:

git log --follow FILE

Screenshots

No response