So, you’ve mastered Git. You work with it on a regular basis and operations like merging and rebasing is second nature to you. You feel comfortable using Git and people tend to come to you for Git related questions.
But now you’ve been asked to incorporate Git from scratch in a new project where a lot of people will be working together. This raises a lot of questions:
• What should the scope of your Git repository be?
• Mono repository or multiple small repositories?
• With multiple repositories how do we make system wide changes in a controlled matter? Are there alternatives?
• With our team, what will our branching strategy look like? Do we default to merging or rebasing?
• How is branching different with a project that is still in development compared to a project that is in maintenance mode?
I will also give some tips and tricks that I do in my project
• Using the SHA within Git to uniquely identify your releases.
• Using tooling to enable semantic versioning for your projects
This training is meant for team leads, architects or other roles that want to lift their knowledge about Git to a higher level.
