Timeline for Clean code vs clean git/jira history
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 18, 2018 at 7:10 | comment | added | findusl | because the answer of Jacob made good points why they shouldn't be in the same ticket. My question didn't make those points but rather stated the rule that someone figured out who knows more than me. | |
| Dec 18, 2018 at 6:52 | comment | added | Doc Brown | @findusl: my answer is for the question as it is written. Now, in your comment you tell us a different story - not the Jira tickets being the problem, but code reviews. That is a different problem, but it has been asked here and answered before, like here: softwareengineering.stackexchange.com/questions/380925/… | |
| Dec 17, 2018 at 14:09 | comment | added | findusl | The issue tracker is associated with merges. Or rather multiple commits are associated with one task, because we use rebase instead of merge. But as Jacob correctly mentioned above, doing the changes on the same task/merge/rebase will result in them being in the same code review where they don't belong. It will be bigger than necessary and all together may be rejected, meantime someone else uses the function etc. | |
| Dec 17, 2018 at 13:22 | history | answered | Doc Brown | CC BY-SA 4.0 |