I see no reason to use this if you commit often and know how to use reflog.
Dura is a background process that watches your Git repositories
11–20 of 207 posts
Re: Dura is a background process that watches your Git repositories
#12Seems like a nice tool, but if you really used git, I don't really see how this situation described at the readme.md could happen :-) you think you just lost days of work
Any unstaged work is getting committed in the background, so if you lose unstaged work accidentally, it will be available on that dura branch.
Re: Dura is a background process that watches your Git repositories
#13Took me a while to realize this is derived from the word duraBILITY. At first I thought this was a russian word being used...
The root is Latin, duro, which means hard. https://en.m.wiktionary.org/wiki/duro#Latin
Re: Dura is a background process that watches your Git repositories
#14I’ve had this idea for about 10 years - it really pays off to wait and eventually someone will build all my ideas :) There are many things to build on top: - Squash history so that it doesn’t grow indefinitely. - Be somewhat language aware to provide better commit messages - IDE integration
Fossil has had this feature for a long time
Re: Dura is a background process that watches your Git repositories
#15This is an interesting concept. I'd think it would need some kind of system tray icon to be aware if it stops running, otherwise, it might provide a false sense of security and you could lose work because you thought you were safe but Dura actually crashed three days ago. It also probably needs some sort of automatic syncing to a remote repo, so it isn't affected by spilling your coffee on your laptop.
If there was a machine-parseable `dura status` command, a Hammerspoon menu bar icon could poll that every N seconds and make a status icon!
Re: Dura is a background process that watches your Git repositories
#16Took me a while to realize this is derived from the word duraBILITY. At first I thought this was a russian word being used...
I thought it was called дура (stupid) because 'git' is slang for idiot.
Re: Dura is a background process that watches your Git repositories
#17Seems like a nice tool, but if you really used git, I don't really see how this situation described at the readme.md could happen :-) you think you just lost days of work
Not for you and me but might save hours/days of work for someone (including me-a-few-years-ago) who is lazy/forgetful about their commits.
"including me-a-few-years-ago". This also applies to me, sometimes you have to learn the hard way. I would say that in this scenario addressing the root cause is better than treating the symptoms.
Re: Dura is a background process that watches your Git repositories
#18Along similar lines, I've adopted a hyper-frequent commit pattern in git. I do a bunch of meaningless micro-commits as I'm making progress, and then rewrite them all into one or two meanginful commits once I've reached a working state of whatever I was trying to do. I find it's helpful for not losing work / easily backing up if as I'm going along I realize I want to change approach. (For the micro commit I have a git…
Might be a useful workflow for you to use fixup commits to rebase automatically helps you out
Re: Dura is a background process that watches your Git repositories
#19No post body was provided.
Re: Dura is a background process that watches your Git repositories
#20I see no reason to use this if you commit often and know how to use reflog.
So then don't use it.
I prefer not rebasing / editing unless I have to.