Whether you are on your own or with a team, having an efficient Git workflow can go a long way to boost your productivity.
For the past month, I've...
For further actions, you may consider blocking this person and/or reporting abuse
In addition, with my old team we did wrote thoses practices into the definition of done of our project.
It gave us the possibility to reject a pull request because of bad commits.
It lead us to be more conscientious about our git workflow and history :)
Great article! Thank you, Christopher! I'm starting to use the label thing in my team focusing on the status of each pull request such as (Abandoned, Blocked, Review Needed, Revision Needed). Do you automate the labeling part?
Hey Zakiah, I'm glad you enjoyed the article ! We do not automate this part no, neither in their creation or the assignment.
Whenever we open a new PR we take the time to set the labels one by one as it's important not to mess it up.
Nice read! The header image really attracts me so i have to know.. what tool is that? Or is it vscode with some extension?
I used a tool I made called Banner generator 😁
Haha okay not the header image, the git timeline thingy i meant! I've starred the Banner generator :D
Oh my bad ! It's just a picture from Unsplash 😅 thanks for the star !
It is a vs code extension, git graph: marketplace.visualstudio.com/items...
Ah thanks that's why it looked familiar, i've seen that before :)
For branches, I like what @ben does -
ben/fix-analyticsSource: github.com/thepracticaldev/dev.to
Thanks for this! I heard pre-commit.com is pretty valuable too.