You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gitea supports viewing the line-by-line revision history for a file also known as blame view.
21
+
You can also use [`git blame`](https://git-scm.com/docs/git-blame) on the command line to view the revision history of lines within a file.
22
+
23
+
1. Navigate to and open the file whose line history you want to view.
24
+
1. Click the `Blame` button in the file header bar.
25
+
1. The new view shows the line-by-line revision history for a file with author and commit information on the left side.
26
+
1. To navigate to an older commit, click the  icon.
27
+
28
+
## Ignore commits in the blame view
29
+
30
+
All revisions specified in the `.git-blame-ignore-revs` file are hidden from the blame view.
31
+
This is especially useful to hide reformatting changes and keep the benefits of `git blame`.
32
+
Lines that were changed or added by an ignored commit will be blamed on the previous commit that changed that line or nearby lines.
33
+
The `.git-blame-ignore-revs` file must be located in the root directory of the repository.
34
+
For more information like the file format, see [the `git blame --ignore-revs-file` documentation](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt).
35
+
36
+
### Bypassing `.git-blame-ignore-revs` in the blame view
37
+
38
+
If the blame view for a file shows a message about ignored revisions, you can see the normal blame view by appending the url parameter `?bypass-blame-ignore=true`.
0 commit comments