CST 438 Week 3 Learning Journal
Git for source code management
Git is a great distributed version control system as it supports collaborative development. Each developer will have a copy of the repository and can work offline locally before sharing it with the group via the central server. Git's branching system allows developers to manage features without affecting their colleagues' work. Logs and a history of changes are kept of every change that happens and who made the change, which allows for effective communication if there are any questions. Git also keeps track of the versions of a project. Team members have access to all committed versions from the first to the most recent.
In addition to what was mentioned above, Git also allows programmers to merge their work with that of other programmers. Merge will combine programmers' work so that all files have the same code. The issue with using merge is that conflicts can arise if two programmers change the same line of code in a file. It is up to the programmer to manually take care of the conflicts before continuing with the merge. In addition to the merge conflicts, programmers need to be aware that a successful merge does not mean that the code will run. It means that two programmers did not change the same line in the file. It is possible that after the merge, the code will not run. A programmer must test the program after the merge to confirm that the changes were successful.
Comments
Post a Comment