{"id":28371,"date":"2023-04-23T05:48:48","date_gmt":"2023-04-23T05:48:48","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=28371"},"modified":"2023-04-23T05:49:07","modified_gmt":"2023-04-23T05:49:07","slug":"what-is-git-and-how-it-works-an-overview-and-its-use-cases","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/what-is-git-and-how-it-works-an-overview-and-its-use-cases\/","title":{"rendered":"What is Git and How it works? An Overview and Its Use Cases?"},"content":{"rendered":"\n

What is Git?<\/h2>\n\n\n\n

Git is a free and open-source distributed versions control system use to handle small to very laravel projects code enabling multiple developers to work together. Git additionally makes cooperation simpler, permitting changes by numerous individuals to be generally converged into one source. Git is generally utilized for both open source and business programming improvement, with huge advantages for people, groups and organizations.<\/p>\n\n\n\n

History & Origin of GIT<\/h2>\n\n\n\n

History. Git development began in April 2005, after many developers of the Linux kernel gave up access to BitKeeper, a proprietary source-control management (SCM) system that they had been using to maintain the project since 2002.<\/p>\n\n\n\n

How Git works<\/strong>?<\/h2>\n\n\n\n
    \n
  1. Initialize a Git repository: You can initialize a Git repository in a directory by running the git init<\/code> command. This creates a hidden .git<\/code> directory in your project folder, which contains all the metadata that Git uses to keep track of your files.<\/li>\n\n\n\n
  2. Track files: Once you have a Git repository, you can start tracking files by adding them to the staging area with the git add<\/code> command. This tells Git to start tracking changes to those files.<\/li>\n\n\n\n
  3. Make changes: You can modify files in your project folder as you normally would. Git will keep track of any changes you make.<\/li>\n\n\n\n
  4. Stage changes: When you’re ready to commit changes to the repository, you can stage them by running the git add<\/code> command again. This tells Git to prepare those changes for commit.<\/li>\n\n\n\n
  5. Commit changes: To actually save your changes to the repository, you can run the git commit<\/code> command. This creates a new commit in the repository with the changes you’ve staged.<\/li>\n<\/ol>\n\n\n\n

    Git Architecture and Workflow?<\/h2>\n\n\n\n

    In Git, there are three main areas where changes to files can be tracked: the workspace, the staging area, and the repository.<\/p>\n\n\n\n

      \n
    1. Workspace:<\/strong> The workspace is where you edit your files. It’s simply the directory on your local machine where your project files are stored. Any changes you make to your files in the workspace are not tracked by Git until you add them to the staging area.<\/li>\n\n\n\n
    2. Staging area:<\/strong> The staging area, also known as the index, is a temporary storage area where Git tracks changes to files that are ready to be committed. When you use the git add<\/code> command, Git adds the changes you’ve made in the workspace to the staging area. Once you’ve added all the changes you want to commit, you can then use the git commit<\/code> command to permanently save those changes to the repository.<\/li>\n\n\n\n
    3. Repository:<\/strong> The repository is where Git permanently stores your project files and their complete history. When you commit changes in Git, a new snapshot of your project files is created and stored in the repository. This snapshot includes all the changes that were added to the staging area. You can use the git log<\/code> command to view the commit history of the repository, which shows all the changes that have been made to the files in the repository over time.<\/li>\n<\/ol>\n\n\n\n
      \"\"<\/figure>\n\n\n\n


      <\/h2>\n\n\n\n
      \"Git<\/figure>\n\n\n\n
      \"\"<\/figure>\n\n\n\n
      \"\"<\/figure>\n\n\n\n

      Use case of Git<\/strong><\/p>\n\n\n\n