From aliases, to commits, to commit messages, to reviews, to workflows.
> Something about it being not in your editor makes you spot more bugs and left-over print statements.
That's so true. I also always read my own changes in the browser, before I hand it over for review... weird
That's awesome! Thanks for sharing your approach. How do you resolve merge conflicts when you have them? I found that lazygit did a pretty good job for me when I needed to resolve a conflict.
> Something about it being not in your editor makes you spot more bugs and left-over print statements.
That's so true. I also always read my own changes in the browser, before I hand it over for review... weird
That's awesome! Thanks for sharing your approach. How do you resolve merge conflicts when you have them? I found that lazygit did a pretty good job for me when I needed to resolve a conflict.