When splitting the pane, al my (uncommitted) git changes are removed.

[ronaldgj]

Discord username (optional)

No response

Describe the bug

All my changes are lost when I'm splitting a pane during coding.

So when I'm working on something, sometimes I need another pane. When I hit Cmd + d, it is splitting, but then all my changes are gone. And it sais: Updated 4 paths from the index. (The 4 is because I had 4 files at the moment).

I've had this problem more often.

To Reproduce

1. In Warp go to the Git project folder.
2. Do some changes in your code.
3. Go to Warp en split the pane. (CMD + D on Mac)
4. My settings are that a new pane will open in the same folder as where you are splitting it from.
5. Then you will see that some paths are updated and all the changes are gone.

Expected behaviour

I should expect that it not should update my Git.

Screenshots

Operating System

MacOS

OS Version

13.1

Shell Version

zsh 5.8.1 (x86_64-apple-darwin22.0)

Warp Version

v0.2023.01.03.08.03.stable_01

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

[elviskahoro]

@ronaldgj can you share a video? i'm not able to reproduce this

[vorporeal]

@ronaldgj Do you have any aliases for git that might be causing this?

[ronaldgj]

Hi! Sorry for my absence. Was on holiday.

I cannot reproduce it at this time. I restarted my macbook and then opened Warp. I can see the splitted pane again when I quitted it to restart my macbook.

Now it has this message in one of the panes:

[ronaldgj]

@ronaldgj Do you have any aliases for git that might be causing this?

Don't know. I use some aliases like gc to use git checkout. But it only happens when I open a new pane / restart Warp. It looks like it want to do something with Git 🤔

[vorporeal]

Does this happen in other git repositories or just this one? If you run git init to create a fresh repository, do you encounter any odd git-related issues there?

At the start of each block, we attempt to determine if you're in a git repository and the name of the current branch, which is probably what is triggering this behavior.

I'm wondering if something got this specific repository into a bad state (e.g.: some other git command you ran created a lock file but didn't clean it up) and that's leading to odd behavior in Warp when we run git rev-parse --abbrev-ref HEAD.

[ronaldgj]

Ok, I tested it with my aliases I use for git (I have 4) and one of them is triggering this issue. I have this alias:
alias gcreset="$(gc $(git ls-files -m))".

But I don't actually understand why it is executing this one when I start Warp. It also happens when I quit Warp en start Warp.

Then I commented out al the aliases involving git and it seems this one is the one who is causing the problem.

I don't use it actually, so I removed it. But I'm wondering what to do, to fix it! 🙂

[ronaldgj]

Does this happen in other git repositories or just this one? If you run git init to create a fresh repository, do you encounter any odd git-related issues there?

At the start of each block, we attempt to determine if you're in a git repository and the name of the current branch, which is probably what is triggering this behavior.

I'm wondering if something got this specific repository into a bad state (e.g.: some other git command you ran created a lock file but didn't clean it up) and that's leading to odd behavior in Warp when we run git rev-parse --abbrev-ref HEAD.

I made a empty repo and tested it. Then I have the same issue. So it looks like it has to do with my comment above.