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

At least once a month, when modifying some critical piece of code - git blame is the easiest way to find reasons for non-obvious lines of code.

BTW: if you sometimes move code around between two git repos (from multirepo to monorepo for example), I wrote a script to move a subfolder between the two and keep history:

https://github.com/jakub-g/git-move-folder-between-repos-kee...




Oh that's a cool tool. I'll try to remember it next time.




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

Search: