Timeline for Is it ever OK to commit non-working code?
Current License: CC BY-SA 4.0
34 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 2, 2022 at 9:44 | history | edited | Vorac | CC BY-SA 4.0 |
added 2 characters in body
|
| Jun 16, 2020 at 10:01 | history | edited | CommunityBot |
Commonmark migration
|
|
| May 1, 2020 at 6:20 | history | edited | Vorac | CC BY-SA 4.0 |
edited body
|
| Jan 23, 2018 at 16:33 | history | protected | gnat | ||
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot |
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
|
|
| Feb 15, 2017 at 19:33 | review | Close votes | |||
| Feb 20, 2017 at 3:03 | |||||
| Feb 15, 2017 at 19:07 | comment | added | user22815 | Possible duplicate of Is it good idea to require to commit only working code? | |
| Apr 14, 2015 at 11:05 | history | edited | Michael Durrant |
edited tags
|
|
| Apr 13, 2015 at 23:47 | history | tweeted | twitter.com/#!/StackProgrammer/status/587764146042707969 | ||
| Apr 13, 2015 at 15:43 | comment | added | Joshua Taylor | "Why? What is the value of a broken commit?" The ability to have identified a problem and test multiple different resolutions on top of it and to be able to reliably go back to the problem that you knew you had, rather than a state where you've got that and maybe some new ones, too. | |
| Sep 29, 2013 at 14:25 | audit | First posts | |||
| Sep 29, 2013 at 14:26 | |||||
| Sep 18, 2013 at 9:36 | vote | accept | Vorac | ||
| Sep 17, 2013 at 7:45 | answer | added | CodeGnome | timeline score: 3 | |
| Sep 17, 2013 at 7:44 | history | edited | Vorac | CC BY-SA 3.0 |
added 156 characters in body
|
| Sep 17, 2013 at 7:36 | history | edited | Vorac | CC BY-SA 3.0 |
added 336 characters in body
|
| Sep 16, 2013 at 22:16 | comment | added | Andy Hunt | I've committed non-working code so another developer can take over a task to free me up to do another before, though that's a specific scenario. | |
| Sep 16, 2013 at 21:53 | answer | added | dukeofgaming | timeline score: 15 | |
| Sep 16, 2013 at 17:07 | answer | added | Sean McSomething | timeline score: 6 | |
| Sep 16, 2013 at 15:42 | answer | added | Igbanam | timeline score: 0 | |
| Sep 16, 2013 at 15:20 | answer | added | Michael Shaw | timeline score: 5 | |
| Sep 16, 2013 at 15:15 | answer | added | CodeART | timeline score: 0 | |
| Sep 16, 2013 at 15:00 | answer | added | user40980 | timeline score: 26 | |
| Sep 16, 2013 at 12:46 | comment | added | Neil | "you are the sole developer on the project" -- You have your answer. If you're the only one who is going to see your code, whether or not you should commit broken code is entirely your choice. | |
| Sep 16, 2013 at 12:24 | review | Close votes | |||
| Sep 24, 2013 at 3:01 | |||||
| Sep 16, 2013 at 12:07 | comment | added | gnat | unless you define what makes commit "broken", it is impossible to authoritatively answer this question. See also: Should a programmer fix someone else's failed build? | |
| Sep 16, 2013 at 11:56 | answer | added | Michael Durrant | timeline score: 10 | |
| Sep 16, 2013 at 11:30 | answer | added | WarrenT | timeline score: 48 | |
| Sep 16, 2013 at 10:44 | comment | added | Joachim Sauer | if you develop each feature on its own branch, then that decision is trivial: discard the branch, continue from a new branch created on the current master | |
| Sep 16, 2013 at 10:19 | comment | added | Vorac | @Joachim Sauer, maybe "nightmare" was a little over the top. Git is very nice. This is the scenario: (1) I start writing code for a small feature (2)I commit regularly in the local repo (3) I decide not to implement the feature / to take entirely different approach (4) I don't really know where to revert to! | |
| Sep 16, 2013 at 10:09 | comment | added | Joachim Sauer | Reverting is a nightmare? What VCS do you use? With git it's quite trivial (not that it's a good thing, if you do that often, but the VCS should at least not make it harder). And locally you can compile whatever you want. For example if you want to try something and have a semi-sane starting point. | |
| Sep 16, 2013 at 9:52 | comment | added | Vorac | @Joachim Sauer, I am asking about best practices and reasoning behind them, in order to build up good habits. Currently I often commit broken code. And reverting is a nightmare, through the tens of commits for the past couple of days. | |
| Sep 16, 2013 at 9:44 | answer | added | nvoigt | timeline score: 4 | |
| Sep 16, 2013 at 9:32 | comment | added | Joachim Sauer | In local branches everything goes. Commit whatever you want. Just clean up before you push. | |
| Sep 16, 2013 at 9:29 | history | asked | Vorac | CC BY-SA 3.0 |