Git and GitHub Terms and Diagrams - Presenter Steve Baskauf

Oct 26, 2026

Upload by Grenda

A set of Git and GitHub instructional diagrams and terms describing how remote and local repositories interact through pull, push, cloning, and committing. Covers core concepts such as staging, direct commits, branches and commits, and a typical work cycle of pulling at start and pushing at end. Explains collaboration models, variation based on number of collaborators and access rights, how issues relate to commits, and how branching helps avoid version conflicts.

LanguageEnglish

CategoryTechnology

FormatPDF

Pages14

Reading Time35 min

AccessFree to download

The World of Git and GitHub

Remote and Local Repositories

Work Cycle: Pull Then Push

Collaboration and Version Conflicts

Issues Tracker and Commits

Branching and Shared Repository Models

website: [vanderbi.lt/github](vanderbi.lt/github) Git and GitHub terms and diagrams Presenter: Steve Baskauf [steve.baskauf@vanderbilt.edu](steve.baskauf@vanderbilt.edu) The World of Git and GitHub remote repository on GitHub web interface direct commit online pull push local computer Git drive staging folder add file area commit repository on local drive Local version control for disaster prevention local computer Git drive staging folder add file area commit repository on local drive Variation in use of GitHub • Depends on number of collaborators in the group • Depends on who has write access to the repository • Depends on social conventions established by the group Disaster prevention via synching with GitHub (1 user) online copy of repository remote repository on GitHub pull push pull push clones of GitHub repository repository on home computer repository on work computer Branches and commits branch commits time Work cycle • Always start a work session by pulling changes from GitHub • Always end a work session by pushing changes to GitHub Simple collaboration (>1 user) online copy of repository Warning! High probability of version conflicts! remote repository on GitHub pull push pull push clones of GitHub repository repository on contributor A's computer repository on contributor B's computer The issues tracker • Issues generally represent problems to be solved to achieve some goal. • In GitHub, resolution of an issue usually results in at least one commit. • One can think of there being a direct relationship between issues and commits . • The GitHub issues tracker is closely integrated with its system for managing changes . Shared repository model (>1 user) Used when all collaborators have write access to the repo on GitHub. B's branch main branch A's branch branching main branch A's branch B's branch main branch Version conflicts avoided when working on separate branches

FAQs

What is the recommended work cycle when using GitHub?

Start a session by pulling changes from GitHub, and end the session by pushing changes to GitHub.

How do issues relate to commits in GitHub?

Issues generally represent problems to solve to reach a goal, and resolving an issue usually results in at least one commit.

How can branching help avoid version conflicts?

Working on separate branches reduces the chance of version conflicts by keeping changes isolated until coordination through integration is needed.

Oct 26, 2026

Upload by Grenda