| Age | Commit message (Collapse) | Author |
|---|
|
We don't actually use it to do map lookups; we still iterate over it in the same
way as before. However, using a map makes it easier to patch elements; see the
next commit.
|
|
|
|
|
|
stefanhaller/discard-changes-only-from-local-commits
Allow discarding changes only from local commits
|
|
We use CommitFilesController also for the files of commits that we show
elsewhere, e.g. for branch commits, tags, or stashes. It doesn't make sense to
discard changes from those (for stashes it might be possible to implement it
somehow, but that would be a new feature), so we disallow it unless we are in
the local commits panel.
|
|
stefanhaller/better-prompt-for-discarding-old-file-changes
Better prompt for discarding old file changes
|
|
Lazygit knows what kind of file change this is, so there doesn't have to be any
"if" in the prompt text.
|
|
Discarding changes to an entire directory doesn't quite work correctly in all
cases; for example, if the current commit added files to the directory (but the
directory existed before) then those files won't be removed.
It might be possible to fix the command so that these cases always work for
directories, but I don't think it's worth the effort (you can always use a
custom patch for that), so let's display an error for now.
|
|
|
|
I don't know why we were setting the initial context to CurrentSideContext
and not just CurrentContext in the first place. If there is no current context
in either case it'll default to the files context. So the only issue is if
we anticipated that some random context would be focused and we didn't want to
activate that. But I can't think of any situation where that would happen.
|
|
|
|
|
|
|
|
fix kakoune binary name
|
|
|
|
|
|
|
|
Whenever we perform an action in a test, we should assert on the result before doing the next action.
This prevents issues where the test moves too fast for our code. It would be nice to not have to do this,
but for now that's the situation
|
|
|
|
|
|
|
|
jesseduffield/refresh-commits-viewport-on-focus-lost
|
|
A better refactor would be to allow matchers to assert against either a string or a slice of cells, so that I could have
the same ergonomics that I have elsewhere, but this is a start.
|
|
The root commit is special in that it has no parents. So we need to add a pipe that's headed for a commit
that doesn't actually exist i.e. the mythical empty tree commit. We're using the actual hash of that
pseudo-commit, but it's not being read anywhere.
|
|
We don't want the highlighted selection sticking around after the context loses focus.
|
|
VSCode had an issue in their terminal where underscores were printed all over the place.
That has now been fixed.
See https://github.com/jesseduffield/lazygit/issues/2294 and https://github.com/xtermjs/xterm.js/issues/4238
|
|
|
|
|
|
|
|
'white' is great on dark themes, and terrible on light themes.
|
|
|
|
Show menu instead of prompt when there are conflicts in a rebase or merge
|
|
This solves the issue that previously you could too easily abort a rebase
accidentally by hitting escape.
|
|
|
|
Add --all to "git fetch" command, unless disabled by config.
|
|
|
|
|
|
No change in behavior.
|
|
These were never used, since there are separate functions for fetching a remote
and for fast-forwarding a branch.
|
|
|
|
|
|
|
|
|
|
jesseduffield/dependabot/go_modules/golang.org/x/net-0.7.0
|
|
We've given Uffizzi a go but haven't found utility in it, so we're removing it.
|
|
|
|
jesseduffield/custom-command-suggestions-from-commands
|
|
|
|
The menuFromCommand option is a little complicated, so I'm adding an easy way to just use the command output directly,
where each line becomes a suggestion, as-is.
Now that we support suggestions in the input prompt, there's less of a need for menuFromCommand, but it probably still
serves some purpose.
In future I want to support this filter/valueFormat/labelFormat thing for suggestions too. I would like to think a little more
about the interface though: is using a regex like we currently do really the simplest approach?
|
|
This changes the interface a bit but it was only added earlier today so I doubt anybody is dependent on it yet.
I'm also updating the docs.
|
