{"id":28424,"date":"2022-03-09T06:33:24","date_gmt":"2022-03-09T06:33:24","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=28424"},"modified":"2022-12-23T06:48:00","modified_gmt":"2022-12-23T06:48:00","slug":"what-is-github-and-how-it-works-an-overview-and-its-use-cases","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/what-is-github-and-how-it-works-an-overview-and-its-use-cases\/","title":{"rendered":"What is Github and How it works? An Overview and Its Use Cases?"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

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

GitHub is a free personal and official, cloud-hosted platform for code. It works with Git on your and your colleagues’ computers, serving as the origin, the source of truth for anyone working on the code. GitHub is a website where you can upload a copy of your Git repository. It allows you to collaborate much more easily with other people on a project. GitHub is a great place to not only expand your programming knowledge, but also showcase your best work. Your GitHub Profile is a great place for recruiters to find you and reach out about potential jobs and projects.<\/p>\n\n\n\n

History & Origin of GitHub<\/strong><\/h2>\n\n\n\n

Development of the GitHub.com platform began on October 19, 2007<\/strong>. The site was launched in April 2008 by Tom Preston-Werner, Chris Wanstrath, P. J. Hyett and Scott Chacon after it had been made available for a few months prior as a beta release. GitHub has an annual keynote called GitHub Universe.<\/p>\n\n\n\n

How works GitHub architecture<\/strong><\/h2>\n\n\n\n
\"DevSecOps<\/figure>\n\n\n\n

Use case of GitHub<\/h2>\n\n\n\n

There are a number of key concepts that you\u2019ll need to understand to work effectively with Git and GitHub. Here is a list of some of the most common terms with a short description of each and an example of how they might be used in conversation:<\/p>\n\n\n\n

Commit<\/strong><\/p>\n\n\n\n

Whenever you save your changes to one or more files to history in Git, you create a new commit. Example usage: \u201cLet\u2019s commit these changes and push them up to GitHub.\u201d<\/p>\n\n\n\n

Commit message<\/strong><\/p>\n\n\n\n

Every time you make a commit, you need to supply a message that describes why the change was made. That commit message is invaluable when trying to understand later why a certain change was implemented. Example usage: \u201cMake sure to include Susan\u2019s comment about the new SEC guidelines in the commit message.\u201d<\/p>\n\n\n\n

Branch<\/strong><\/p>\n\n\n\n

An independent series of commits off to one side that you can use to try out an experiment or create a new feature. Example usage: \u201cLet\u2019s create a branch to implement the new search functionality.\u201d<\/p>\n\n\n\n

Master branch (master)<\/strong><\/p>\n\n\n\n

Whenever you create a new Git project, there is a default branch created that is called master. This is the branch that your work should end up on eventually once it\u2019s ready to push to production. Example usage: \u201cRemember never to commit directly to master.\u201d<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Feature and Advantage of using<\/strong> GitHub<\/strong><\/h2>\n\n\n\n