The changes you each make won't be visible to one another until you explicitly make them visible, by merging them to a common branch. You could work on a branch called profile-pics, and he could be working on a branch called quotes. Let's say you're adding a profile pictures to the application, and another guy is adding favorite quotes. It allows you to create a separate "swim lane" for your files, so you can work on something in isolation, then merge it back to the main line when you're sure it works. It's basically a more powerful (and more efficient) way of doing MySourceCodeV1/, MySourceCodeV2/, MySourceCodeV3, and so on.īranching is a bit cooler. You can compare the current version to a previous version, or even go back to the previous version, to see what was different and make necessary changes. Let's say adding that new functionality broke something in the UI. Git allows you to check out previous versions of your work. Then you change them, either adding functionality, adding another chapter, or whatever. You start with a set of files, which could be a program, a bunch of chapter files for a novel, pretty much anything. GitHub offers two big advantages: version control and branching.
0 kommentar(er)
