Jesse Duffield

I'd say that github sponsors is basically the same as patreon (i.e. recurring sponsors) but it doesn't seem likely to generate enough ongoing support to be able to support a...

Thanks for all the great points @peppy @mark2185 @sdegutis . Regarding kickstarter, I don't think it's out of the ordinary for a kickstarter to be used as a kick-continuer based...

@mark2185 good point. If updates come along with an in-app changelog and an dev-diary-ish update that could help out (and I don't think it would be very intrusive either: for...

thanks @MikaelElkiaer and @jbrains, I really appreciate the donations (and kind words)! On the topic of suggesting more features, that's a very good point. I'm going to start writing some...

@lalitsharmaking for how-to questions you should create a new discussion in the discussions tab (https://github.com/jesseduffield/lazygit/discussions)

Alas, the defaultBranch config option only applies to when we're creating a new repo, not when we're dealing with an existing one. We'll need to wait and see if git...

@PGScully I agree. In the case where both exist I would use master. I feel like in repos where `main` has been opted for, it's less likely that we'll see...

Yep, this issue is about colouring commits based on whether they're included in the main branch, whether that's master or main. This is a harder problem to solve (efficiently) without...

@kittydoor I like the idea of defining a default ordering, with the ability to specify the main branch on a per-repo basis. So we could we have: ```yml mainBranchPrecedence: ['main',...

Yep if we get an actual error back from git we should just surface that. If we don't get an error back, then I'd parse the output for the version