7 Important Git Command
1. git clone
A command used in the Git version control system to create a copy of a remote Git repository on your local machine. The syntax for using the command is:
>> git clone <repository-url>
where <repository-url> is the URL of the remote Git repository that you want to clone.
When you run the 'git clone' command, Git will create a new directory with the same name as the remote repository in your current directory, and download all of the repository's files and commit history into that directory. You can then make changes to the files, commit those changes, and push them back to the remote repository using Git commands.
2. git pull
A command used in the Git version control system to fetch and merge changes from a remote Git repository into your local branch. The syntax for using the command is:
>> git pull [<options>] [<repository> [<refspec>…]]
By default, 'git pull' will fetch changes from the remote repository specified in the configuration file for the current branch, and merge them into the local branch. If there are any conflicts between the local and remote changes, Git will attempt to automatically merge them, but you may need to manually resolve any conflicts that arise.
You can also specify a remote repository and/or a branch or commit to pull changes from, using the <repository> and <refspec> options respectively.
It's important to note that 'git pull' is actually a combination of two other Git commands: 'git fetch', which downloads the latest changes from the remote repository, and 'git merge', which merges those changes into your local branch. If you prefer, you can run these two commands separately instead of using 'git pull'.
3. git checkout
A command used in the Git version control system to switch between different branches or commits in a Git repository. The syntax for using the command is:
>> git checkout <branch or commit>
where '<branch or commit>' is the name of the branch or the hash of the commit you want to switch to.
If you're switching to a branch that already exists in your local repository, Git will update your working directory to match the latest version of that branch. If you're switching to a specific commit, Git will put your repository in a "detached HEAD" state, which means you'll be at a specific commit but not on any branch.
You can also use 'git checkout' to create a new branch based on the current one, by specifying the '-b' option and a name for the new branch:
>> git checkout -b <new-branch-name>
This will create a new branch with the given name and switch to it.
It's worth noting that in more recent versions of Git, the 'git switch' command has been introduced as a more streamlined way to switch between branches. 'git switch' essentially does the same thing as 'git checkout', but with a simplified syntax and clearer behavior.
4. git add
A command used in the Git version control system to stage changes made to files in your working directory, preparing them to be committed to the repository. The syntax for using the command is:
>> git add <file>
where '<file>' is the name of the file you want to stage. You can also use the '.' character to stage all changed files in the current directory and its subdirectories.
Once you've added changes to the staging area with 'git add', you can use the 'git commit' command to permanently save those changes to the Git repository. Running 'git add' again on a file that has already been staged will add any new changes you've made to that file to the staging area.
You can use the 'git reset' command to unstage changes that you've previously staged with 'git add'. To unstage a specific file, you can use the command:
>> git reset <file>
To unstage all files that you've staged with 'git add', you can use the command:
>> git reset
It's important to note that the 'git add' command only stages changes for the next commit. If you want to permanently remove changes from your working directory, you can use the 'git rm' command to delete the file and stage the deletion.
5. git commit
A command used in the Git version control system to save changes made to files in your working directory to the Git repository. The syntax for using the command is:
>> git commit -m <message>
where '-m' is an optional flag to add a commit message, and '<message>' is the message you want to associate with the commit. If you don't include the '-m' flag, Git will open your default text editor so you can enter a commit message.
When you run the 'git commit' command, Git will create a new commit with the changes you've staged using the 'git add' command. Each commit has a unique hash that identifies it, and contains a snapshot of the repository at the time of the commit, along with metadata such as the author, timestamp, and commit message.
It's good practice to write clear and descriptive commit messages that explain the changes you've made. This can be especially helpful for other developers who may need to understand why certain changes were made, or for your future self if you need to revisit the repository later.
Once you've committed changes to the repository, you can use the 'git push' command to push those changes to a remote Git repository and make them available to others.
6. git push
A command used in the Git version control system to upload local repository changes to a remote Git repository. The syntax for using the command is:
>> git push [<remote>] [<branch>]
where '<remote>' is the name of the remote repository you want to push to (usually "origin"), and '<branch>' is the name of the branch you want to push your changes to.
When you run the 'git push' command, Git will upload all of the commits that you've made to the specified branch in the remote repository. If the branch doesn't exist in the remote repository, Git will create it.
If there are conflicts between your local changes and changes that have been made to the remote repository since your last pull, Git will prevent you from pushing your changes until you've resolved the conflicts. In this case, you'll need to use the 'git pull' command to download the latest changes from the remote repository, resolve any conflicts, and then try pushing your changes again.
It's worth noting that you may need to authenticate yourself with the remote repository before you can push changes. This typically involves providing your username and password or setting up an SSH key for authentication.
7. git branch
A command used in the Git version control system to manage branches in a Git repository. The syntax for using the command is:
>> git branch <new-branch-name>
>> git branch -d <branch-name>
When run without any arguments, the 'git branch' command will display a list of all the branches in the repository, highlighting the branch that you're currently on with an asterisk.
If you specify a branch name as an argument, Git will create a new branch with that name based on the current branch you're on. For example, running 'git branch my-new-branch' will create a new branch named "my-new-branch" that's based on the branch you're currently on.
You can also use the '-d' flag followed by a branch name to delete a branch. For example, running 'git branch -d my-old-branch' will delete the branch named "my-old-branch".
To switch to any different branch, you can use the 'git checkout' command. For example, running 'git checkout my-other-branch' will switch you to the branch named "my-other-branch".
You can also use the '-b' flag followed by a branch name to create a new branch and switch to it in a single command. For example, running 'git branch -b my-new-branch' is equivalent to running 'git branch my-new-branch' followed by 'git checkout my-new-branch'.
In addition to managing branches, the 'git branch' command can also be used to display information about branches, such as their most recent commit, or to list remote branches using the '--remote' or '-r' flag.
What is GIT & GIT HUB :- https://info-tech-sl.blogspot.com/2023/03/git-git-hub.html
Additional read :- GIT - Center for High Performance Computing - The University of Utah
إرسال تعليق