@darius this is one of the main things I try to communicate to junior devs: write verbose git commits! and make them a clean discrete idea as much as possible. all code is about communication and the commit message is a handy tool to figure out wtf the code is on about. I didn’t know about the ability to see the diff while writing! gonna update my alias
@christa Yes! I emphasize that doing this writes 90% of your pull request for you ahead of time, and it does so while your brain is still inside the specific task of coding so you are in the best place to explain what you were doing and why. The PR itself then just becomes a place to contextualize the commit(s) within the larger feature you are PR'ing.