Nice article. The recommended tutorial looks really helpful. For me, the main hardness of Git is the workflow. When it's fine to commit? What is an optimal way of using branches? And so on... Surprisingly, I can't find any course on Git based on some real project and teaching this. Do you know any such resource? Thank you.
I really don't know a great course on the git 'strategies,' and I clearly should write my next article about this!
I'll give you the short answer now: your git workflow is going to be a reflection of your team's workflow. Even a basic component like branching and merging shouldn't be used if they're not what make sense for your team. If you're working solo, it may not make sense to use branching unless your project is becoming extremely complicated.
Nice article. The recommended tutorial looks really helpful. For me, the main hardness of Git is the workflow. When it's fine to commit? What is an optimal way of using branches? And so on... Surprisingly, I can't find any course on Git based on some real project and teaching this. Do you know any such resource? Thank you.
I really don't know a great course on the git 'strategies,' and I clearly should write my next article about this!
I'll give you the short answer now: your git workflow is going to be a reflection of your team's workflow. Even a basic component like branching and merging shouldn't be used if they're not what make sense for your team. If you're working solo, it may not make sense to use branching unless your project is becoming extremely complicated.
Appreciate your response and clarification of some issues. Looking forward to the article.