Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Surprisingly light on version control best practices.

1. Big commits make it easier to evade code reviews, submit pull requests close to the deadline

2. Commit messages should be generic and misleading

3. Logical units of change should be split up between many non consecutive commits, big commits should contain multiple different features and bugfixes

4. Have bots commit to version control frequently

5. Keep multiple copies of the same files for backup

6. Rename and move around files frequently

7. Reuse filenames liberally



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

Search: