Hacker News new | past | comments | ask | show | jobs | submit login

Fore removing code that's buggy in production. It's way easier to find and remove 1 commit.



Isn’t that what rolling back releases for? i.e. revert the container (or whatever your unit of release is) to the previous version? If you’re removing individual commits and re-releasing (rolling forward), you’re still at risk of being down, because you’re not going back to a known good release.


And what do you think about the linked article that shows how it's easier to find exactly which code is buggy if you have it in small commits instead of one big squashed one?


Good, do what he did too... but in a feature branch.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: