| Hard Prerequisites |
| IMPORTANT: Please review these prerequisites, they include important information that will help you with this content. |
|
|
In this topic, we will be covering a few of the more common commands that are used regularly along with their uses.
Git commands are the magic spells you cast on your repository to perform a wide array of tasks, from creating copies of a repository to tracking changes and collaborating with others. Let’s focus on the most frequently used commands:
git clonegit clone is your first step into the world of an existing project. This command is used to create a local copy of a remote repository. It’s like downloading a folder from the internet, except this folder is a Git repository.
git clone <repository-url>
git statusgit status is the command you’ll use to get a quick overview of what’s happening in your repository. It tells you which changes have been staged, which haven’t, and which files aren’t being tracked by Git.
git status
git branchBranching is one of Git’s standout features, allowing you to diverge from the main line of development and work independently. git branch lets you create, list, and delete branches.
git branch <branch-name> # Create a new branch
git branch # List all branches
git pullgit pull updates your local repository to the newest commit from the remote repository. It’s a way of synchronising your work with others, ensuring you’re all building on the latest version.
git pull origin <branch-name>
git pushAfter you’ve made changes and committed them, git push sends your commits to the remote repository. This shares your work with the team, contributing to the collective project.
git push origin <branch-name>
git commit -mgit commit is how you save your changes. Think of it as taking a snapshot of your project at a specific point in time. The -m flag allows you to attach a message to your commit, explaining what you’ve done.
git commit -m "Your message here"
In Git, origin is the default name given to the remote repository from which your local repository was cloned. It’s like a nickname for the URL of the remote repository, making it easier to reference.
Branching allows you to create separate lines of development. Imagine it as having a main storyline (master or main branch) and several side stories (other branches). You can work on new features, bug fixes, or experiments in branches without affecting the main project. Once you’re satisfied with the changes in a branch, you can merge it back into the main storyline.
To check whether your commit works as intended, you can use:
git diff: This command shows the differences between your working directory and the index (the area where changes are staged), helping you review what changes you’ve made.git diff