Timeline for When to commit code?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 2, 2016 at 9:29 | comment | added | tdammers | Yes, but to a lesser degree, because (see original answer) you won't disturb anyone directly. Depending on the SCM in question, it's usually considered good practice to clean up your commit history before merging upstream though (e.g. git rebase -i). | |
| Apr 27, 2016 at 8:41 | comment | added | Juha Untinen | I presume the same applies for new branches, where all new development is commited to your own branch, which you will then push when the feature is ready? Ie. you might commit even a lot of incomplete code to your own private branch. | |
| Jun 14, 2011 at 15:42 | history | answered | tdammers | CC BY-SA 3.0 |