diff options
| author | Stefan Haller <stefan@haller-berlin.de> | 2023-07-27 14:15:56 +0200 |
|---|---|---|
| committer | Stefan Haller <stefan@haller-berlin.de> | 2023-07-29 11:59:58 +0200 |
| commit | f30e09856cb14ee4b6ec4457588e960e4f52eb24 (patch) | |
| tree | c69052f00084a85441109623066374187c64c0bc /pkg/i18n | |
| parent | 9b7f978e3e305908d4c8da21462e3b7974346d66 (diff) | |
Add bisect menu entry that lets you choose bisect terms
This can be useful if you want to find the commit that fixed a bug (you'd use
"broken/fixed" instead of "good/bad" in this case), or if you want to find the
commit that brought a big performance improvement (use "slow/fast"). It's pretty
mind-bending to have to use "good/bad" in these cases, and swap their meanings
in your head.
Thankfully, lazygit already had support for using custom terms during the bisect
(for the case that a bisect was started on the command-line, I suppose), so all
that's needed is adding a way to specify them in lazygit.
Diffstat (limited to 'pkg/i18n')
| -rw-r--r-- | pkg/i18n/english.go | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/pkg/i18n/english.go b/pkg/i18n/english.go index 735ac3cf4..2d0fb90e8 100644 --- a/pkg/i18n/english.go +++ b/pkg/i18n/english.go @@ -552,6 +552,9 @@ type Bisect struct { ResetTitle string ResetPrompt string ResetOption string + ChooseTerms string + OldTermPrompt string + NewTermPrompt string BisectMenuTitle string Mark string Skip string @@ -1350,6 +1353,9 @@ func EnglishTranslationSet() TranslationSet { ResetTitle: "Reset 'git bisect'", ResetPrompt: "Are you sure you want to reset 'git bisect'?", ResetOption: "Reset bisect", + ChooseTerms: "Choose bisect terms", + OldTermPrompt: "Term for old/good commit:", + NewTermPrompt: "Term for new/bad commit:", BisectMenuTitle: "Bisect", CompleteTitle: "Bisect complete", CompletePrompt: "Bisect complete! The following commit introduced the change:\n\n%s\n\nDo you want to reset 'git bisect' now?", |