GitHub glossary: Learn important terminology
Below are examples of important terminology from the GitHub glossary:
- Repository: A repository is the most basic element of GitHub. They're easiest to imagine as a project's folder. A repository contains all of the project files (including documentation), and stores each file's revision history. Repositories can have multiple collaborators and can be either public or private.
- Branch: A branch is a parallel version of a repository. It is contained within the repository, but does not affect the primary or main branch allowing you to work freely without disrupting the "live" version. When you've made the changes you want to make, you can merge your branch back into the main branch to publish your changes.
- Commit: A commit, or "revision", is an individual change to a file (or set of files). When you make a commit to save your work, Git creates a unique ID (a.k.a. the "SHA" or "hash") that allows you to keep record of the specific changes committed along with who made them and when. Commits usually contain a commit message which is a brief description of what changes were made.
- Pull request: Pull requests are proposed changes to a repository submitted by a user and accepted or rejected by a repository's collaborators. Like issues, pull requests each have their own discussion forum.
- Fork: A fork is a personal copy of another user's repository that lives on your account. Forks allow you to freely make changes to a project without affecting the original upstream repository. You can also open a pull request in the upstream repository and keep your fork synced with the latest changes since both repositories are still connected.
The GitHub Docs page has links to further learning resources offered, like documentation on Repositories, and Pull requests. For a tutorial on using repositories, branches, commits and pull requests go to the Hello World Tutorial.
- Review the content in the GIS Pantry _start-here folder.
- Start by reading the GIS_Pantry_QuickStart Doc
BC Open Source Development Employee Guide
- Principles for Participation
- Browsing and Consuming Material in GitHub
- Approval Requirements
- Approaches to Collaborating/Contributing
- Appropriate Use
- Conflict of Interest, Privacy and Intellectual Property
- Licenses
- Security
BCGov GitHub Organization "How To"
- Guidance
- Templates
- Check Lists