7 commits

Author	SHA1	Message	Date
Jesse Duffield	26ca41a40e	Handle pending actions properly in git commands that require credentials ... I don't know if this is a hack or not: we run a git command and increment the pending action count to 1 but at some point the command requests a username or password, so we need to prompt the user to enter that. At that point we don't want to say that there is a pending action, so we decrement the action count before prompting the user and then re-increment it again afterward. Given that we panic when the counter goes below zero, it's important that it's not zero when we run the git command (should be impossible anyway). I toyed with a different approach using channels and a long-running goroutine that handles all commands that request credentials but it feels over-engineered compared to this commit's approach.	2023-07-08 22:54:52 +10:00
TomCao New Macbook Pro	3d79c6a3d3	formatter	2022-09-17 15:10:41 -07:00
jiepeng	b8900baf1a	remove deprecated calls	2022-09-17 15:10:41 -07:00
Jesse Duffield	a936c0592f	more refactoring	2022-01-09 14:09:53 +11:00
Jesse Duffield	18f48a43d5	add some more linters	2022-01-09 14:09:53 +11:00
Jesse Duffield	fdf79fdeee	fix bug that caused credentials popup to be raised unexpectedly	2022-01-09 14:09:53 +11:00
Jesse Duffield	f503ff1ecb	start breaking up git struct	2022-01-09 14:09:53 +11:00