3 ms·
From what I see you just agree with my comment. Those 5 commits you described as example are the way I would do it. The way it is described in article would ma
by ozim 9y ago
From what I see you just agree with my comment. Those 5 commits you described as example are the way I would do it.
The way it is described in article would make you do it in one commit and add information that would be in the ticket.
- deiwin 9y agoWhat makes you say that? The Focused rule from the article is also meant to persuade you to split the work into similarly concise and focused commits.
- ozim 9y agoFocused and complete are opposite. You can have focused commits or complete commits.
- deiwin 9y agoAlso, the ticket and the commits can provide answers to the same questions without being redundant. The answers are just at a different level of abstraction and for different readers. Tickets usually describe product-level decisions, while commits describe implementation-specific details. E.g. a ticket may discuss alternative user flows, while a related commit explains why a specific algorithm, module, or default configuration value was used.