Tracked file (tracked files)
A tracked file is a file in a working directory (repository) managed by Git. When you add new files or make updates to existing files, Git keeps track of those file changes. At some point in time, you will submit these files to the Git repository by command.
Commit (Commit)
The commit operation is the process of adding changes to the tracked files to the Git repository. You need to fill in the summary and instructions, and then add the file to the Git library. Git maintains all the history of repository submissions.
Submission instructions (Commit message)
The submission description is a summary and description of the set of files that are currently being submitted.
Merge (Merging)
Merging is the process of fusing code from one branch to another. When you have finished modifying and refining your code in a branch, you will typically want to merge the main branch back into your code. Git provides an authentication tool that displays code changes to assist with the merge process.
Changeset (change sets)
Git lets you see all the file changes under the current branch. You can view the changes and decide which file changes you want to submit to the branch.
For example, you may have completed two of the five change files and need to submit these two files separately. You submit these two files, Git will record this history and continue to track changes in other files. This allows you to create a logical changeset instead of simply basing the change on the date.
Submit record (Commit history)
Git logs all the changes that have been committed so that you can check for all previous changes. If you clone a git library, you'll also copy the commit record.
Summarize
The basic git process is to create a git library, make changes and add actions, and then commit as a changeset. Git will report changes to the tracked files, letting you decide how to organize the submissions. Once you have completed some commits, you can check the status of your project by checking the commit record of git.
Chapter One part 2/2 Git at a glance