Luka Markušić
Luka Markušić
> The folder returned by lazygit --cd only contains config.yaml for me. Okay, I might have been mistaken about the `--cd` flag then, my bad. > but I guess it...
> If a repositories is moved somewhere else (path in state.yaml does not exist anymore) `lazygit` will remove invalid paths from `state.yml` on launch, so that would explain why they're...
Is moving repos around something you do often? If so, why? 🤔
Alrighty then, I'd definitely suggest to explore the possibility of symlinks, so that you don't have to move the plugins here and there but just link and unlink. I'm not...
@Ridermansb according to [the docs](https://github.com/jesseduffield/lazygit/blob/master/docs/Config.md), on MacOS it should be in `~/Library/Application\ Support/lazygit/`?
Just out of curiosity, is this a PR across forks? The assumption is that the original repo is on the `origin` remote, whilst the fork is on `upstream`, if I'm...
Is that really `lazygit`'s fault if your git service didn't protect the branch? It just does `git push` in the background.
Under which name does `git push fork` push the branch? E.g. if you are on a branch `performance_fix` and do `git push fork`?
> It will push to whatever the upstream is set to for the current branch. You can check it with git branch -vv: [SO link](https://stackoverflow.com/q/4950725/9196137) That's probably dictated by your...
Ah, now I get it. For the time being, you can press `ctrl+a` to jump to the beginning of the line and use `delete` to delete the `origin` part and...