mirror of
https://github.com/jesseduffield/lazygit.git
synced 2025-05-12 12:55:47 +02:00
5b613f5bc7
Previously the entire status was colored in a single color, so the API made sense. This is going to change in the next commit, so now we must include the color in the string returned from BranchStatus(), which means that callers who need to do hit detection or measure the length need to decolorize it. While we're at it, switch the order of ↑3↓7 to ↓7↑3. For some reason that I can't really explain I find it more logical this way. The software out there is pretty undecided about it, it seems: VS Code puts ↓7 first, and so does the shell prompt that comes with git; git status and git branch -v put "ahead" first though. Shrug. |
||
|---|---|---|
| .. | ||
| fetch_prune.go | ||
| fetch_when_sorted_by_date.go | ||
| force_push.go | ||
| force_push_multiple_matching.go | ||
| force_push_multiple_upstream.go | ||
| force_push_remote_branch_not_stored_locally.go | ||
| force_push_triangular.go | ||
| pull.go | ||
| pull_and_set_upstream.go | ||
| pull_merge.go | ||
| pull_merge_conflict.go | ||
| pull_rebase.go | ||
| pull_rebase_conflict.go | ||
| pull_rebase_interactive_conflict.go | ||
| pull_rebase_interactive_conflict_drop.go | ||
| push.go | ||
| push_and_auto_set_upstream.go | ||
| push_and_set_upstream.go | ||
| push_follow_tags.go | ||
| push_no_follow_tags.go | ||
| push_tag.go | ||
| push_with_credential_prompt.go | ||
| rename_branch_and_pull.go | ||
| shared.go | ||