My opinion falls more in line with Ryan's and this guy's from an article called "Thou Shalt Not Lie: git rebase, amend, squash, and other lies" [1].
[1] http://paul.stadig.name/2010/12/thou-shalt-not-lie-git-rebase-ammend.html?m=1 Brandon On Mon, May 11, 2015, 5:54 PM Sean Busbey <[email protected]> wrote: > On Mon, May 11, 2015 at 4:26 PM, Ryan Blue <[email protected]> wrote: > > > I disagree. I think we all agree there's value to having separate > commits, > > but logical breakdown of a task often goes into detail that, when > mirrored > > into JIRA without reason, is just busy work. > > > > > > What value does an issue provide if there is no discussion and it is just > > a box to tick when working on another issue? > > > > rb > > > > > > I don't think we all agree there's value to having separate commits. The > time when I think it's valuable is precisely when the sub-tasks are > actually something that might benefit from additional discussion or reviews > on jira. > > -- > Sean >
