When we use most source code managem ent systems (git, Subve rsion, Concurrent Versioni ng System).

When we store new or changed file(s) in a creating a new "version" or "revision", we call this action a When doing so, we should always add a descriptive summary of what was changed or why, since the summary will show in the history. If we undo changes to one or more files being tracked in the VCS, this operation is called The action to create a local copy of an online repository is called if the result allows us to track local file changes and easily compare differences between the local and online repository later. The action of bringing more recent changes from that online repository to our local one is called Suppose 2 or more people are working with such a shared online repository. One sends changes and then the other person tries to send theirs before accounting for the first person's. To resolve that, the second person must do a pull (aka update) and then a before retrying to send their changes. Git is a DISTRIBUTED version control system, thus more complex than SVN and CVS for example. The following features apply to git and GitHub. We can derive our own online instance of someone else's repository which we can then use and manage independently, but have it stay linked to theirs -- we call that derived instance a If When we want to send changes upstream from our cloned repository to its origin, this action is called a you forget that step, then you will not see your latest changes on GitHub's website. Suppose you have read-only access to a git repository. You want to send the repository owner some revisions that you think they should incorporate into theirs. That action of sending your changes and asking them to use or review them is called a tag merge commit merge conflict revert pull request folder subdirectory unit test repository push dictionary update or pull clone or checkout fork