Dura is a background process that watches your Git repositories
1–10 of 207 posts
Re: Dura is a background process that watches your Git repositories
#2 you think you just lost days of workRe: Dura is a background process that watches your Git repositories
#3Re: Dura is a background process that watches your Git repositories
#4Re: Dura is a background process that watches your Git repositories
#5Re: Dura is a background process that watches your Git repositories
#6Re: Dura is a background process that watches your Git repositories
#7Seems 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
Re: Dura is a background process that watches your Git repositories
#8Re: Dura is a background process that watches your Git repositories
#9There 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
Re: Dura is a background process that watches your Git repositories
#10I 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 command "git cam" that just commits all changes with the message "nt". Then once I'm ready to do a "real commit", I have "git wip" which rolls back all the nt commits but leaves them in checkout; then I can make one or two "real" commits.)
I wonder if dura would be even better, or if the commit frequency would end up being too fine-grained and obscure?