The following are terms commonly used when discussing GeoGig.
- History path containing its own timeline and list of commits. Using multiple branches allows for parallel development.
- Switches to another branch.
- Copy of a repository. While a clone is made from an existing repository, there is no hierarchy between them.
- A snapshot of changes made to files in a repository. Commits have a timestamp, an author, a description, and contain a diff of the files changed.
- Contradictory state of a repository. Usually caused by merging from different branches.
- Shows specific differences between two commits. Can also contain commits included between them on the timeline.
- Loads information about a repository into a data source, such as a shapefile or database.
- See pull.
- Loads information about a data source (such as a shapefile or database) into a GeoGig repository.
- History of a repository, containing a list of commits, unique IDs, and metadata about the committer.
- Default branch name. In a common workflow, branches are created from the master branch and then merged back in at a later time
- Combines commits from one branch onto another branch.
- Process to receive commits and branches from a remote repository
- Process to send commits and branches to remote repository
- Other repository that is linked to the current repository. Repositories that linked as remotes can execute a pulls or pushes to each other.
- Manages history and allows for “rolling back” commits.
- Displays details about a single commit.
- The history of commits over time.
Previous: 5.1. Resources
Boundless provides commercial open source software for internet mapping and geospatial application development. We are dedicated to the growth and support of open source software.
This work is licensed under a Creative Non Commercial-Commons Attribution-Share Alike 3.0 United States License. Feel free to use this material, but we ask that you please retain the Boundless branding, logos and style.