Work with Teams in GitHub | Git and GitHub Basics
#salesforce
#trailhead
#salestraining
Git and GitHub Basics: • Git and GitHub Basics
Now that you’ve gone through a simple GitHub flow example on your own, imagine how the workflow will work with a team. Multiply all of the branches, commits, and pull requests by the number of colleagues on your team and by active development. Many teams have done this before, and there are patterns that show success over time.
In general, branches should be short lived, created to accomplish a function, and deleted once they're merged. Short-lived branches prevent confusion, encourage up-to-date code, and set up developers for iterative improvements to projects.
Long-running branches can create problems if not used intentionally. Sometimes a long-lived branch make sense for a development branch, or for other situations when you need multiple levels of deployment-level code. Most of the challenges with long-running branches come from developers not having the most up-to-date version of each branch, creating needless merge conflicts, confusion, and work. While more complex branching workflows might seem like the right solution, they’re frequently over-complicated and the simpler GitHub flow works more effectively.
Watch video Work with Teams in GitHub | Git and GitHub Basics online without registration, duration hours minute second in high quality. This video was added by user Saurabh Infotech Solutions 27 November 2022, don't forget to share it with your friends and acquaintances, it has been viewed on our site 5,075 once and liked it 10 people.