- \n
- git init command<\/strong>
Initializes a new Git repository within a directory. Using it without a [name]<\/strong> will initialize a repo using the current directory’s name:<\/li>\n<\/ul>\n<\/div><\/div>git init [name]<\/pre>
- \n
- git add command<\/strong>
Stages file changes, preparing them for the next commit:<\/li>\n<\/ul>git add <filename><\/pre>
- \n
- git commit<\/strong>
Saves staged changes to the local repository (a process called a commit<\/strong>) and can include a descriptive message about the modifications:<\/li>\n<\/ul>git commit -m \"your commit message\"<\/pre>
- \n
- git status<\/strong>
Shows the current state of your working directory and staging area, including which files have been modified, staged, or are untracked:<\/li>\n<\/ul>git status<\/pre>
- \n
- git log<\/strong>
Displays a chronological list of commits in the current repository, showing details such as commit messages, authors, and timestamps:<\/li>\n<\/ul>git log<\/pre>
- \n
- git diff<\/strong>
Shows the differences between items in various states of a repository, such as your current working directory and the most recent commit:<\/li>\n<\/ul>git diff [file-branch-directory-or-commit] [file-branch-directory-or-commit]<\/pre>
- \n
- git rm<\/strong>
Removes files from your working directory and stages the removal for the next commit:<\/li>\n<\/ul>git rm <filename><\/pre>
- \n
- git mv<\/strong>
Renames or moves files within your working directory. It behaves similarly to Linux’s mv command and has a similar syntax:<\/li>\n<\/ul>git mv <filename> <filename-or-directory><\/pre>
- \n
- git config<\/strong>
Changes the settings of various aspects of your Git installation, including user information and preferences. For example, use this to set your email address for commits:<\/li>\n<\/ul>git config --global user.email \"your.email@example.com\"<\/pre>
\n💡Prefer using a graphical interface?<\/h4>\n
While commands offer flexibility and efficiency, some users prefer using a graphical user interface (GUI) to visualize how version control works. In this case, consider using one of the best Git GUI clients<\/a>. <\/p>\n <\/div>\n\n\n\n<\/p>
Git branching and merging commands<\/h2>
“Branching and merging commands let you work on different features or fixes simultaneously. They make it easy to integrate changes and maintain a clean, organized project history.<\/p>
- \n
- git branch<\/strong>
Manages branches in your Git repository. For example, you can list, create, or rename a branch<\/a>. Run this command as-is to list all branches:<\/li>\n<\/ul>git branch [--options] [branch-name]<\/pre>
- \n
- git checkout<\/strong>
Switches between branches and restores files from different commits. Here’s an example to switch to an existing branch:<\/li>\n<\/ul>git checkout branch_name<\/pre>
- \n
- git merge<\/strong>
Combines a feature or topic branch into the main branch. Below is an example of basic git merge usage:<\/li>\n<\/ul>git merge branch_name<\/pre>
- \n
- git cherry-pick<\/strong>
Applies specific commits from one branch to another without merging an entire branch. It selects a specific commit using its hash:<\/li>\n<\/ul>git cherry-pick commit_hash<\/pre>
- \n
- git rebase<\/strong>
Applies changes from one branch to another by moving or combining commits, helping maintain a cleaner commit history. For example, this will apply commits from your current branch to the main branch:<\/li>\n<\/ul>git rebase main<\/pre>
- \n
- git tag<\/strong>
Marks specific points in your Git history, such as version releases like v1.0 or v2.0. An example command looks like this:<\/li>\n<\/ul>git tag v1.0<\/pre>
Git remote repository commands<\/h2>
Remote commands connect your local repository to external ones like GitHub<\/a> or GitLab. They allow you to share your work, collaborate with others, and synchronize changes between environments.<\/p>
- \n
- git clone<\/strong>
Creates a copy of a remote repository on your local machine. For example, the most common git clone usage is to download a repository from GitHub:<\/li>\n<\/ul>git clone https:\/\/github.com\/username\/my-project.git<\/pre>
- \n
- git push<\/strong>
Sends your local branch commits to a remote repository, updating it with your latest changes. For example, to push changes from the local “main” branch to the remote repository named “origin”:<\/li>\n<\/ul>git push origin main<\/pre>
- \n
- git pull<\/strong>
Fetches and integrates changes from a remote repository into your current local branch. Here’s an example to pull changes from the master branch:<\/li>\n<\/ul>git pull origin master<\/pre>
- \n
- git fetch<\/strong>
Retrieves new commits from a remote repository without automatically merging them into your current branch. Here’s an example:<\/li>\n<\/ul>git fetch origin<\/pre>
- \n
- git remote<\/strong>
Manages remote repositories associated with your local repository. Running the basic syntax will list remote repositories, but you can add options and subcommands to complete other tasks:<\/li>\n<\/ul>git remote [options] [subcommand] [args]<\/pre>
- \n
- git submodule<\/strong>
Manages separate repositories embedded within a Git repository. For example, use this to add a submodule to your main repository:<\/li>\n<\/ul>git submodule add https:\/\/github.com\/username\/submodule-repo.git submodule\/path\/on\/main-repo<\/pre>
Advanced Git commands<\/h2>
Advanced commands offer greater control over your repository’s history and workflow. They’re used for tasks like rewriting commits, troubleshooting issues, and optimizing project structure.<\/p>
- \n
- git reset<\/strong>
Undoes changes and manipulates the commit history, useful when recent modifications contain an error. Here’s a basic example to unstage changes made to a file:<\/li>\n<\/ul>git reset <filename><\/pre>
- \n
- git stash<\/strong>
Temporarily saves changes that aren’t yet ready to be committed. You can add subcommands likelist<\/code> to view stored changes andpop<\/code> to reapply them to your working directory:<\/li>\n<\/ul>git stash [subcommand]<\/pre>
- \n
- git bisect<\/strong>
Identifies bugs or issues in your project’s history through a binary search process. Use this to start the bisecting process:<\/li>\n<\/ul>git bisect start<\/pre>
- \n
- git blame<\/strong>
Identifies the most recent change to each line of a file and the associated author. This is helpful for tracking down when and by whom specific changes were made:<\/li>\n<\/ul>git blame file1.txt<\/pre>
- \n
- git reflog<\/strong>
Shows a log of reference updates in your repository, allowing you to track your repository’s history, even when commits appear to be deleted or lost:<\/li>\n<\/ul>git reflog<\/pre>
- \n
- git clean <\/strong>
Removes untracked files or directories from your working directory, helpful for organizing your repository. For safety, use the-n<\/code> option first to preview what will be deleted, then confirm with the-f<\/code> option:<\/li>\n<\/ul>git clean [options]<\/pre>
Git commands cheat sheet<\/h2>
If you’re just starting out, remembering Git commands can be challenging. To help you master this tool, we’ve created a Git cheat sheet<\/a> you can download or print out. Keep it handy whenever you need a quick reference for Git commands.<\/p>
What is the easiest way to install Git on Ubuntu?<\/h2>
- git clean <\/strong>
- git reflog<\/strong>
- git blame<\/strong>
- git bisect<\/strong>
- git stash<\/strong>
- git reset<\/strong>
- git submodule<\/strong>
- git remote<\/strong>
- git fetch<\/strong>
- git pull<\/strong>
- git push<\/strong>
- git clone<\/strong>
- git tag<\/strong>
- git rebase<\/strong>
- git cherry-pick<\/strong>
- git merge<\/strong>
- git checkout<\/strong>
- git branch<\/strong>
- git config<\/strong>
- git mv<\/strong>
- git rm<\/strong>
- git diff<\/strong>
- git log<\/strong>
- git status<\/strong>
- git commit<\/strong>
- git add command<\/strong>
![\"Kodee](\"\/tutorials\/wp-content\/uploads\/sites\/2\/2017\/03\/kodee-vps-ai-assistant-provides-commands-for-installing-and-configuring-git-641x1024.png\")