KEDEHub glossary

This glossary introduces common Git and KEDEHub terminology.

access token

A token that is used in place of a password when performing operations over HTTPS with KEDEHub on the command line or the user interface. Also called a personal access token.

authentication code

A code you'll supply via the browser. This code is either generated by an application or delivered to your email adddress.


The user-generated description found on a profile: Adding a bio to your profile

billing cycle

The interval of time for your specific billing plan.

billing email

The organization email address where KEDEHub sends receipts, credit card or PayPal charges, and other billing-related communication.

billing manager

The organization member that manages billing settings for an organization.

billing plan

Payment plans for users and organizations that include set features for each type of plan.

Business plan

An organization billing plan.

child team

Within nested teams, the subteam that inherits the parent team's access permissions.


A clone is a copy of a repository that lives on your computer instead of on a website's server somewhere, or the act of making that copy. When you make a clone, you can edit the files in your preferred editor and use Git to keep track of your changes without having to be online. The repository you cloned is still connected to the remote version so that you can push your local changes to the remote to keep them synced when you're online.

code of conduct

A document that defines standards for how to engage in a community.


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.

commit author

The user who makes the commit.

commit ID

Also known as SHA. A 40-character checksum hash that identifies the commit.

commit message

Short, descriptive text that accompanies a commit and communicates the change the commit is introducing.


A time-based job scheduler in Unix-like computer operating systems.


Your personal dashboard is the main hub of your activity on KEDEHub.

email notifications

Notifications sent to a user's email address.

enterprise account

Enterprise accounts allow you to centrally manage policy and billing for multiple KEDEHub organizations.


A fast-forward is a special type of merge where you have a revision and you are "merging" another branch's changes that happen to be a descendant of what you have. In such a case, you do not make a new merge commit but instead just update to this revision. This will happen frequently on a remote-tracking branch of a remote repository.


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.

Free plan

A user account billing plan that is free.


Git is an open source program for tracking changes in text files. It was written by the author of the Linux operating system, and is the core technology that KEDEHub utilizes.

Git Importer

A tool that quickly imports source code repositories, including commits and revision history, to KEDEHub for users.


A plain .git file, which is always at the root of a working tree and points to the Git directory, which has the entire Git repository and its meta data. You can view this file for your repository on the command line with git rev-parse --git-dir. that is the real repository.


Human-readable nicknames that correspond to the address of a device connected to a network.


A document that you can include with your project to let people know what they can and can't do with your source code.

locked personal account

A personal account that cannot be accessed by the user. Accounts are locked when users downgrade their paid account to a free one, or if their paid plan is past due.

management console

A section within the KEDEHub Enterprise interface that contains administrative features.


A new copy of a repository.

nested team

A child team of a parent team. You can have multiple children (or nested) teams.


Updates, delivered by either the web or email depending on your settings, that give you information about the activities you're interested in.

open source

Open source software is software that can be freely used, modified, and shared (in both modified and unmodified form) by anyone. Today the concept of "open source" is often extended beyond software, to represent a philosophy of collaboration in which working materials are made available online for anyone to fork, modify, discuss, and contribute to.


Organizations are a group of two or more users that typically mirror real-world organizations. They are administered by users and can contain both repositories and teams.

organization owner

Users who have full administrative access to the organization they own.


The default upstream repository. Most projects have at least one upstream project that they track. By default, origin is used for that purpose.


Organization members that have complete administrative access to the organization.

parent team

Within nested teams, the main team from which child teams inherit access permissions and @mentions.

A permanent static hyperlink to a particular web page.

personal account

A KEDEHub account that belongs to an individual user.

primary email address

The main email address where KEDEHub sends receipts, credit card or PayPal charges, and other billing-related communication.


The page that shows information about a user's activity on KEDEHub.

profile photo

A custom image users upload to KEDEHub.

public project

A public project can be viewed by anyone, including people who aren't KEDEHub users.


Pull refers to when you are fetching in changes and merging them. For instance, if someone has edited the remote file you're both working on, you'll want to pull in those changes to your local copy so that it's up to date. See also fetch.


To reapply a series of changes from a branch to a different base, and reset the HEAD of that branch to the result.


This is the version of a repository or branch that is hosted on a server. Remote versions can be connected to local clones so that changes can be synced.

remote repository

A repository that is used to track the same project but resides somewhere else.

remote URL

The place where your code is stored: a repository, another user's fork, or even a different server.


A repository is the most basic element of Git. 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.

root directory

The first directory in a hierarchy.


A user or organization's KEDEHub plan.


A group of organization members that reflect your company or group's structure with cascading access permissions and mentions.


When talking about a branch or a fork, the primary branch on the original repository is often referred to as the "upstream", since that is the main place that other changes will come in from. The branch/fork you are working on is then called the "downstream". Also called origin.


Users are people with personal KEDEHub accounts. Each user has a personal profile, and can own multiple repositories, public or private. They can create or be invited to join organizations or collaborate on another user's repository.


A user's handle on KEDEHub.

Getting started