A branch is a pointer to a specific commit. The branch pointer moves along with each new commit you make and only diverges in the graph if a commit is made on a common ancestor commit. Learn More
In Git, the checkout command tells Git which branch or commit you want your changes applied.
Checking out a branch will update your repo’s files to match the snapshot of whichever commit the branch points to. Learn More
The cherry pick command takes changes from a target commit and places them onto the HEAD of your currently checked-out branch. Learn More
The Git clone command is used to make a copy, or clone, of an existing Git repository into a local directory. Cloning in Git will create a new local directory for the cloned repository, copy all contents of the specified remote repository, and checkout an initial branch in the new local repo.
By default, the Git clone command will create a reference to the remote repository named `origin` and create the remote tracking branches, which can all be seen by running `git branch -a`. Learn More
A commit represents a snapshot of your repository at a specific point in time. A commit is performed in Git as a method of applying local file changes to a Git repository after they have been staged in your working directory. Learn More
The Git merge command allows you to incorporate changes made in a branch into any other branch. Learn More
Git Pull will take changes from a remote repository and incorporate them into your currently checked out local branch. When using this command, Git will first run a Git fetch followed by a Git merge. Learn More
Git push is used to upload a local repository’s content to a remote repository.
Additionally, Git push can also be used to delete a remote repository.
The Git rebase command takes a commit, or group of commits, from a source branch and applies them on top of a target branch. Learn More
The Git stash command will take the state of your current working directory and save it on a stack of unfinished changes that can be reapplied at any time. This will revert back to the HEAD commit with a clean working directory. Only tracked files can be stashed. Learn More