This article discuss about git checkout vs git cherry-pick command, and when to use these commands. git checkout command switches between branches or restores working tree files. This command operates upon three distinct entities i.e. files, commits, and branches. Checking out branches is similar to checking out old commits. Files in [...]
git fetch updates your remote-tracking branches under refs/remotes/<remote>/. This operation is safe to run at any time since it never changes any of your local branches under refs/heads. In other words git fetch gathers any commits from the target branch that do not exist in the current branch and stores [...]
git blame show what revision and author last modified each line of a file. Syntax Below is the syntax of this command. git blame [-c] [-b] [-l] [--root] [-t] [-f] [-n] [-s] [-e] [-p] [-w] [--incremental] [-L <range>] [-S <revs-file>] [-M] [-C] [-C] [-C] [--since=<date>] [--ignore-rev <rev>] [--ignore-revs-file <file>] [--color-lines] [...]
HEAD in GIT is a special pointer. It is a pointer to the last commit snapshot. In simple words, it always points to the most recent commit in the current checkout branch. When you checkout to other branch, it is known as the active or current branch. HEAD^ and HEAD~ [...]
Git has a feature called Tags, it provide an excellent, direct, and simple way to mark the code when a specific version gets released during the development life cycle. For more details refer this. git describe command finds the most recent tag that is reachable from a commit. Get Most [...]
Introduction The git checkout command switches between branches or restores working tree files. This command operates upon three distinct entities: files, commits, and branches. Checking out branches is similar to checking out old commits and files in that the working directory is updated to match the selected branch/revision. However, new [...]
Introduction To ignore a class of files that you don’t want Git to automatically add or even show you as being untracked, create a named .gitignore and add entries of those files as shown in following example. $ cat .gitignore *.[oa] *~ First line show the content of file. Second [...]
Git status command is used to know the status of the working tree. It shows the state of your working directory and helps you see all the files which are untracked by Git, staged or unstaged. In other words, Git will show you any difference in the current tree and [...]
The add command marks changes to be included in the next commit. It adds changes to "Staging Area", the contents of which can then be wrapped up in a new revision with the git commit command. However, git add doesn't really affect the repository in any significant way—changes are not actually recorded [...]
Git has three main states that files can reside in i.e. Committed Modified Staged Committed means that the data is safely stored in your local database. Modified means that you have changed the file but have not committed it to your database yet. Staged means that you have marked a [...]