JupyterHub
HomeServicesDocumentationBlog
1.0.0
1.0.0
  • Introduction
  • Determine Your Workflow
  • About Jupyter Notebooks
  • About JupyterHub
  • Computing Policies
  • ❓Help and Support
    • Getting Support
    • FAQ
    • Known Issues/Bugs
    • Instructor's Checklist
    • Additional Resources
  • Getting Started
    • Sign In
    • Import Notebooks
    • Launch a Notebook
    • Launch a Terminal Session
  • Using Your Hub
    • Interface Overview
    • Creating a New Blank Notebook
    • Managing Active Notebooks
    • Shutting Down Server
  • Content Sync via Link
    • Link generation
  • CONTENT SYNC VIA GIT
    • Git Overview
    • Create GitHub Account
    • Set Up Git in JupyterHub
    • Downloading Content
    • Saving and Uploading Content
    • GIT Cheatsheet
  • Github Classroom (Student Guide)
    • Getting Started
    • Getting and Uploading Assignments
  • GitHub Classroom (Instructor Guide)
    • Overview
    • Getting Started
    • Distributing Homework
    • Distributing Lectures
    • Learning Management Systems
  • ADVANCED TOPICS
    • Package Installation
    • Accessing Classic Notebook
    • Slideshow Plugin
    • VSCode
    • SQLite
    • RStudio and Shiny
    • Dash
  • Reproducibility
    • Replicating the Environment
    • Using Docker
Powered by GitBook
On this page
Export as PDF
  1. CONTENT SYNC VIA GIT

Git Overview

PreviousLink generationNextCreate GitHub Account

Last updated 5 years ago

Git is a version control system that enables you to track changes to files. With Git, you are able to revert files back to previous versions, restore deleted files, remove added files and even track down where a particular line of code was introduced.

Git creates a hidden .git folder (in the current folder) to store the details of the file system - this folder contains all the data required to track your files and is known as a repository, or repo.

Git tracks file changes by the user creating a save point, or in Git terms a commit. Each commit takes a snapshot of the current file system. Commits are uniquely identified by a SHA–1 hash. This is a 40 character string which may along the lines of ded7a0db6422d59e9893e975e32275fc36f853daThis hash can be used to track a particular commit within the repository.

Nearly all operations that are performed by Git are in you local computing environment, for the exception of few used purly to synchronize with a remote. Some of the most common git operations are depicted below. In summary a typical flow consists of making changes to your files, staging them via git add, marking a save point via git commit, then finally syncing to your remote (e.g., GitHub) via git push. If you are pushing changes to your remote from multiple places, you can bring changes your most recent version usin git pull, which is the equivalent of doing git fetch followed by a git merge operation