4 ms·

I know that most of the times (ok, all of the times) you'll have more than one commit for any feature you develop. We'll have a small gem or something to do th

by nhocki 15y ago

I know that most of the times (ok, all of the times) you'll have more than one commit for any feature you develop. We'll have a small gem or something to do that. You'll start your work and we'll track your time and at the end make a commit with the time stamp (or use git notes to keep the commits clean). All the commits you do in that time will be "ignored". We don't have this now because we didn't have the time to do this (48 hours is not that much you know). Thanks for the feedback anyway. Well have your comments in mind when developing v2 and the gem.

pilif 15y ago
> We don't have this now because we didn't have the time to do this (48 hours is not that much you know). I didn't intend to bash on your project. I'm sorry if my comment read that way. I was just saying that I, personally, would not want my commits to be tied to an invoice that is most likely going to be read by a non-coder because that would severely hamper the quality of my commits. I do believe though that for other people this might not be as much of an issue - heck it probably wouldn't for me if I were working on different stuff than I'm working on right now. I just wanted to inform the people here not to jump to conclusions but think what this integration might (or might not - depending on their situation) do to their commits. I LOVE it when people like you have a cool idea and follow through; whether the result is usable for me or isn't.
- nhocki 15y ago
  Oh no, no "offense" taken. We really appreciate feedback (all of it). Having people disagree with the app forces us to make it better. About the messy commit messages, that's why git notes may help (keeps your commits clean, but you still don't have to write the invoice entries again and again). Thanks! :-)