💻
How to Use Project Development Tools in a Remote C
  • How to Use Project Development Tools in a Remote Coding Team
  • Trello
    • Introduction to Trello
    • How to use Trello
      • What is Trello?
      • Starting up a Trello Board
      • Lists
      • Cards
  • Visual Studio Code
    • Introduction to Live Share in Visual Studio Code
    • How to use Live Share
      • How to Install
      • How to Use
      • Examples of Use Cases
  • Git & Github - Basics
    • Introduction to Git & GitHub
    • How To Use Git
      • Setting up Git
      • Creating GitHub Repositories
      • Managing Repository Access
      • Syncing with a Local Workspace
  • How to Manage a Codebase with Git
    • Introduction to Branching
    • How To Use Branches
      • What are Branches?
      • Working in Branches
      • Merging Branches
      • Best Practices For Branching
    • Git Codebase Management Cheat Sheet
  • Conclusion
  • Team Biography
  • References
Powered by GitBook
On this page
  • Problem Statement
  • Scope
  • Constraints
  • Background: Version Control, Git, and GitHub

Was this helpful?

Export as PDF
  1. Git & Github - Basics

Introduction to Git & GitHub

PreviousExamples of Use CasesNextHow To Use Git

Last updated 4 years ago

Was this helpful?

Problem Statement

Through using VS Code and Live Share, developers can collaborate on code projects synchronously. However, synchronous collaboration is not always possible. When working as part of large teams it is difficult to find a chunk of time where developers can get together to code synchronously. Developers need a tool where they can work on code asynchronously and keep track of different versions of the code base.

Scope

There is a lot you can do with Git and GitHub but the basic workflow with GitHub is to create a remote repository with GitHub, sync that repository to a local workspace, and commit changes made locally back to the remote repository. This section gives instructions on how to perform this basic workflow and a high level view of the process.

Constraints

Git is entirely free, and while there are paid versions of GitHub, all the actions in this user document can be done with the free version of GitHub.

Background: Version Control, Git, and GitHub

Version control systems are tools that enable developers to work in parallel over shared projects and to synchronize changes that are made in parallel [11]. With version control, developers can collaborate asynchronously. When working as part of large or distributed teams on complex projects, asynchronous collaboration is a necessity. Consequently, version control has become an important tool in the development cycle in industry and academia [11].

Git is a free open source version control system that can store all files and their version history locally, eliminating the need for a central server [12]. Git can be paired with GitHub, a free hosting service for Git repositories, in order to be used for collaborative software development. With Git and GitHub, developers can keep a remote version of their source code which others can download and edit asynchronously. Git and GitHub are not the only tools for version control, but with over 14 million registered users and 35 million repositories, Git and GitHub form one of the most widely used version control paradigms [12].

The Github Logo