Skip to content

Commit 58c7111

Browse files
authored
Update README.md
Comment about blame
1 parent a0c37b6 commit 58c7111

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

README.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -73,6 +73,12 @@ Move cursor around with arrows or by mouse clicking in any area. Commands your i
7373
- `z` - opens stashes panel <picture><source srcset="./icons/sidebar-show-symbolic.svg"><img valign="middle" alt="Push button" src="./icons/sidebar-show-symbolic.svg" width="12"></picture>
7474
- `t` - opens tags window
7575

76+
### Other Commands
77+
- `o` - opens quick repo selector
78+
- `Ctrl` + `o` - opens repo choosing dialog
79+
- `Ctrl` + `b` - blame line under cursor
80+
81+
7682
> [!NOTE]
7783
> Any window above Status window could be closed with `Esc` or `Ctrl-w`
7884
@@ -127,3 +133,6 @@ Hitting `z` or <img class="inline" src="https://raw.githubusercontent.com/keenly
127133

128134
### Tags window
129135
Hitting `t` in Status window brings up Tags window. That window behave as a simple list where you can `c` - create, `k` - delete (as in **K**ill) and `p` - to push tags to remote.
136+
137+
### Blame
138+
Git blame in Stage is a bit strange :smiley: Stage do not want to read your files directly. It only operates on diffs produced by libgit2. So, to view history of some line in code this line must somehow apear in Stage. This means you have to edit or delete this line :smiley:. Or line nearby (each change in git surrounded by 3 lines of context above and below). When you see your line in Stage you can put cursor on it and hit `Ctrl`+`b`. This will open up commit window pointing this line origin. Again, this works in Commit window to: hitting any line (except green one) in Commit window will bring another window with commit which contains this line adding.

0 commit comments

Comments
 (0)