4 ms·
I've written mine up as I've noticed I was repeating myself a bit once my opinions stabilized. See https://jiby.tech/post/my-git-worfklow/ https://jiby.tech/po
by FrenchyJiby 2y ago
I've written mine up as I've noticed I was repeating myself a bit once my opinions stabilized.
See https://jiby.tech/post/my-git-worfklow/ https://jiby.tech/post/my-git-worfklow/
- u5wbxrc3 2y agoVery though out set of guidelines, thank for this. As I learn more optimized workflows and git usage solely through terminal these days I have come to the realizations that even the tips mentioned here seem obvious and considered good practice among many professionals they arent necessarily used by majority. So I do believe all of this is subjective to an extent because using git as objective means to accomplish version control and just that. I personally like conventional commits and have for years because of its simplicity. Keywords such as feat, fix, build, and docs tell me already what I need to know when searching history or how to version next release.
- wesleyd 2y ago> Use the imperative mood in the subject line I like to think of this not as giving an order to the codebase, but as casting a spell.
- rishikeshs 2y agoGreat read!