Hi rh kramer, On Sunday, December 10, 2017 at 1:12:54 PM UTC+1, rh kramer wrote: > > On Saturday, December 09, 2017 11:32:32 PM Russ P wrote: > > > How would it be implemented? I suppose it would be done by the build > > > system. I am using Scala and sbt. Could sbt be made to automatically do a > > > commit every time it builds successfully? I don't see why not. Heck, > maybe > > > it has that feature already and I just don't know it! And perhaps git > could > > > allow for "minor" commits without a comment. At least that would allow > > > someone like me to locate a bug easier. What do you think? > > > > As someone who hasn't done much development in the last 20 years, I think > it is a great idea. (I do write a lot of text documents, and often fail to > make an interim save and later regret it (for any of a number of reasons).) > > > > As far as a comment, without having used git extensively or recently > (maybe 3-4 years ago), I think some sort of automatic comment would be > useful, something like: > > > > "20171210, 07:08, nn.nn.n:8" > > > > The nn.nn.n:8 meaning the 8th automatic commit (on a compile) after named > branch nn.nn.n)" > > > > Or something similar for any named commit (not necessarily a branch. > > > > I know that some or all of that information is fairly easily available, > but, for me, to be able to see it as a comment often seems more convenient. > > > > I think it would also be useful to be able to easily force an "interim" > auto commit if you've made extensive (or difficult) changes without doing a > compilation. > > > > "20171210, 07:08, nn.nn.n:8:3" > > > > The nn.nn.n:8:3 meaning the 3rd interim commit after the 8th automatic > commit (on a compile) after named branch nn.nn.n)" > > > > And, in both cases, git could prompt optional for additional comments (to > be added after the automatic commit message). >
Even in situation without a build system (so no "post build" trigger), like when writing/editing documentation, it should be pretty easy to use any available/simple task scheduler to trigger something like `git commit --all --no-edit --allow-empty-message` I mentioned (or any variation of it), each 5 minutes, for example. But when I think about it more, might be one of the reasons why this functionality isn`t part of core Git yet is also that it`s not really an advised way of using Git - yes, it`s still possible, but there doesn`t seem to be a point in making it any easier, as you would really like people to do something else - for their own sake. And even then, it does really seem pretty easy to do in the first place, even without "official Git configuration" for it. Regards, Buga -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
