GitHub Glossary

Plain-language definitions of common terms for people new to GitHub

Branch

• (n) a version of a repo.

Clone

1. (n) a copy of a repo that retains the history but doesn’t track new changes.
2. (v) to make a copy of a repo that results in a clone.

Commit

1. (n) a saved snapshot of files.
2. (v) to save a snapshot of files.

Conflict

• (n) a situation when changes from two branches (versions) cannot be merged automatically because it’s not clear which changes take precedence. (This requires manual intervention.)

Fork

1. (n) a copy of a repo that retains an ongoing connection to the source repo for comparing and sharing changes.
2. (v) to make a copy of a repo that results in a fork.

GitHub repo

• (n) a collection of files and folders and their related version history on the GitHub server in the cloud.

Issue

• (n) a bug or suggested enhancement.

Local repo

• (n) a collection of files and folders and their related version history on your computer.

Main branch

• formerly master.
• (n) usually the latest official version of the repo. (Main is now the default branch name when creating new repos on GitHub.)

Markdown

• (n) a syntax for structuring content using basic symbols that is readable by both humans and machines.

Merge

• (v) to combine two branches (versions) into one.

Pull

• (v) to get changes from others and incorporate them into your local repo.

Pull request

• (n) a suggestion to update the current version of a repo with one’s changes.

Push

• (v) to send your changes to the GitHub server to be used by others.

README

• (n) the user manual for the repo.

Release

• (n) a version of the repo with some particular significance.

Repository

• also repo.
• (n) a collection of files and folders.

Collaborate on GitHub Join the Lowcode Lounge organization on GitHub