Roughly a year ago I set up a MacBook (Sequoia) and installed Sublime Merge. I switched the Git binary in the preferencens to bundled and as far as I remember that worked.
This month I set up another MacBook (also Sequoia) and confusingly this didn’t work anymore. I just noticed that it also doesn’t seem to work on the first MacBook anymore either. I keep getting “git failed with exit code 1”.
Does anyone else experience this?
Install the macOS Command Line Tools: xcode-select --install
This will install Git to /usr/bin/git
After that I would recommend using Homebrew to manage/update your Git install.
As I said, I’m asking about the bundled Git binary, not a system-installed one, which does work without issues.
G’day @se1,
Thanks for reaching out, and sorry to hear the bundled Git isn’t working as expected.
To help me look into this, could you confirm how you installed Sublime Merge (e.g. via https://www.sublimemerge.com/download, homebrew, or another method)?
Cheers,
- Dylan from Sublime HQ
In both cases it was installed by downloading the ZIP archive from the download page and copying the app into the Applications directory of a pretty much factory new MacBook (besides running through some settings which are all extremely unlikely to cause such an issue). The only other previously installed app was Sublime Text. I don’t have much macOS experience, but I can’t really see where I could possibly go wrong here. There was never a permissions popup that I declined or anything like that.
I would really appreciate if anyone could test this on an M series MacBook so I know if it’s just me or not.
My Debug Information output says:
Using Git: /Applications/Sublime Merge.app/Contents/Resources/Git/bin/git (bundled)
Running it in a terminal gives me:
zsh: bad CPU type in executable
I still feel like this worked at some point last year, but I guess not? Is this only supposed to work on old Intel MacBooks? I don’t see anything on the download page or in the FAQ about it.
G’day @se1,
Just a quick update that I’ve investigated this and resolved the issue. This will be fixed in the next build.
As a workaround for now you can either use the system Git binary, or revert to the previous version (see the show downloads section under each version here: https://www.sublimemerge.com/download).
Thanks for your help reporting this issue!
Cheers,
Dylan from Sublime HQ