Saving changes and tracking history


show more Saving changes and tracking history provides you with in-depth training on Developer. Taught by Michael Lehman as part of the Fundamentals of Software Version Control show less
please wait ...

Saving changes and tracking history

Once you've got your files in, and you can get your files out, the typical workflow when using any Version Control System looks like this in your repository. At Time 1, you can see that there's a file in your repository that contains A, B, and C. Let's say you check it out and then you delete B and you add D. Now when you save your files back into the repository, use a command that's called commit, check in, or update. When you command the Version Control System to save your updated file, it will ask you for a short description of the changes you've made.

This is oftentimes called a commit message, and this is a crucial part of the history of tracking information. The system will store the differences between the two different versions of the file, and you supply the reason. In some systems you can supply a single line, and in some systems you can actually supply not only a single line which is used in short displays, you can also provide an entire document that describes what ...

Saving changes and tracking history
Video duration: 2m 47s 2h 55m Intermediate

Viewers:

Saving changes and tracking history provides you with in-depth training on Developer. Taught by Michael Lehman as part of the Fundamentals of Software Version Control

Subject:
Developer
Software:
Git Mercurial ALM/TFS Perforce
Author:
please wait ...