Timeline for How often should I/do you make commits?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 22, 2024 at 17:23 | comment | added | bas | I did not know about git-bisect. Looks like a very valuable tool! I might change my commit policy just for that. | |
| S Aug 5, 2021 at 14:01 | history | edited | lennon310 | CC BY-SA 4.0 | Fix spelling errors |
| S Aug 5, 2021 at 14:01 | history | suggested | seasonedfish | CC BY-SA 4.0 | Fix spelling errors |
| Aug 5, 2021 at 4:40 | review | Suggested edits | |||
| S Aug 5, 2021 at 14:01 | |||||
| Nov 16, 2015 at 22:34 | comment | added | SMBiggs | Like your thought about branching. Hadn't thought about it that way before. Saves a lot of back-tracking. | |
| Jun 14, 2012 at 2:51 | comment | added | Ida | +1 for mentioning "to detect the commit source of a given regression" | |
| Aug 2, 2011 at 20:29 | comment | added | tdammers | The 'never break the trunk' rule is a bit softer when you're using a distributed SCM, since you can commit locally without doing any damage; the rule then only applies to pushing, not committing. | |
| May 9, 2011 at 13:33 | history | answered | Thibault J | CC BY-SA 3.0 |