• @ mentioned

    Notify individuals on Github with @ in front of the user name

  • API preview

    A way to try out new apis and make changes to existing API methods before they become official Github APIA

  • assignee

    Users assigned to an issue

  • The CA certificate

    A digital certificate issued by a certificate authority (CA) to ensure a valid link between two machines

  • cURL

    Used to transfer data on the command line or in scripts

  • Explorer

    An instance of graphQL,

  • Gist

    Is a shareable file that you can edit, clone, and copy on Github. You can make Gist public or secret, but secret Gist can be used by anyone with a URL

  • Git

    Is an open source project for tracking changes in text files. It is written by authors of Linux systems

  • gitfile

    A plain.git file, always at the root of the working tree, pointing to the git directory and containing the entire Git repository and its metadata. You can view this file in the repository from the command line with git rev-parse –git-dir

  • Github Flavored Markdown

    Github Markdown, used to format text and code in Github

  • Github Jobs

    A Github job site

  • Github Marketplace

    A subsite used by Github users and organizations to purchase and install applications to extend and complement their workflows

  • Github Pages

    Also known as’ pages, ‘static site-hosting services designed to host individual, organizational, or project pages directly from the Github repository

  • Github Wiki

    The part of the Github repository that hosts Wiki-style documents

  • GithubImport tool

    A tool that allows users to quickly import meta-code repositories (including commit and revision records) into Github

  • GithubThe application

    The Github application provides services to the entire organization, using its own identity when they perform functions. They can be installed directly on organizational and user accounts to grant access to a specific repository. They come with detailed permissions and built-in Web hooks

  • GraphQL

    A query language for the API and a runtime that performs these queries against existing data

  • HEAD

    The branch commit defined, usually the latest commit at the top of the branch

  • HEADfree

    Git warns you if you’re working on a floating HEAD, which means Git isn’t pointing to a branch, and any of your commits won’t show up in the commit history.

  • Hello World

    Is a computer program that outputs or displays “Hello World” to the user

  • Jekyll

    A static site generator for a personal, project, or organizational site

  • JekyllTheme selector

    An automated way to select visual themes for Jekyll sites without editing or copying CSS files

  • LFS

    Git Large File Storage is an open-source Git extension for versioning Large files

  • linguist

    Making use of a repository, used to detect blob | language, ignore the binary or special files, inhibiting difference generated in the file, and generate language figure

  • main

    By default, whenever a Git repository is created, a branch named “main” is created and becomes active

  • Markdown

    Is a very simple semantic file format

  • master

    Default branches in Git repositories

  • OAuthThe token

    An access token used in an application to access user information

  • OAuthThe application

    Third-party applications that use access tokens instead of passwords to access user information

  • SSHThe key

    Github is a way to represent yourself to an online server using an encrypted message. Just as your computer uses a unique password to log into other services, Github securely transfers information to your computer using an SSH key

  • webhook

    Github allows you to build or set up Github applications that subscribe to specific events on Github.com. Web hooks provide a way to send notifications to an external Web server whenever a specific operation occurs in a repository or organization. Also known as “service hooks”.

  • webnotice

    Notifications displayed on the Github Web interface

  • The upstream

    When talking about branches or forks, the primary branch of the original repository is often referred to as “upstream” because it is the primary source of other changes. The branch you operate on is called “downstream.”

  • The upstream branch

    The default branch to which the branch is merged (or to which the branch is based). It is configured through branch.

    . Remote and branch.

    . Merge. If the upstream branch of A is source /B, sometimes we say, “A is tracking source /B.”

  • withGithubUse a combination of

    Support for Github integration list

  • The business plan

    An organizational settlement solution where you can work collaboratively on unlimited public and private repositories, allow or require organization members to authenticate to Github using SAML SSO, and configure and revoke configuration access using SAML or SCIM

  • Individual account

    Github accounts belonging to individual users

  • Personal resume

    A user-generated description of a profile

  • The personal data

    A page that displays information about user activity on Github

  • Profile photo

    A custom image that a user uploads to GitHub to identify their activity, usually in conjunction with their username. Also known as head

  • The host name

    A human-readable nickname that corresponds to the address of the device connected to the network

  • Primary email address

    GitHub’s primary email address for sending receipts, credit card or PayPal charges, and other bill-related communications.

  • The theme

    A way to explore repositories of specific subject areas, find projects to work on, and discover new solutions to specific problems

  • Subject branch

    A regular Git branch used by developers to identify development concept lines. Because branches are easy and cheap, it is often a good idea to have multiple small branches, each containing well-defined concepts or incremental but related changes. Also called “feature branching”.

  • Dependent – figure

    A warehouse diagram that shows packages, projects, and warehouses that depend on the common repository

  • warehouse

    The most basic element of Github, the mouth can easily be thought of as a project folder, a repository that contains all project files (including documents) and stores the revision history of each file

  • The warehouse figure

    Visual representation of warehouse data

  • Warehouse maintenance staff

    A person who manages the warehouse, who helps to categorize issues and manage the warehouse using labels and other functions, and who is responsible for updating readme and participation documents

  • Code owner

    Individuals designated as partial repository code owners automatically apply for code owner reviews when someone opens a pull request (in non-draft mode) to make changes to code owned by the code owner

  • Code frequency diagram

    A warehouse map showing the addition or deletion of Meizhou contents from the warehouse history

  • The dashboard

    The personal dashboard is the information center for your activities on Github. After using the personal dashboard, you can track issues and pull requests that you follow or participate in, navigate to your frequently used warehouses and team pages, and learn about recent activities in the warehouses that you follow or participate in. You can also discover new warehouses that are recommended based on the users you care about and the warehouses you annotate.

  • Corporate account

    Corporate accounts allow you to centrally manage policies and billing for multiple GitHub.com organizations

  • coupons

    Github provides code that users or organizations can use to pay for all or part of their subscriptions

  • scope

    OAuth applications can request named permission groups to access public and non-public data

  • Dependency diagram

    A warehouse diagram that shows packages and items from the warehouse

  • cloning

    A copy of the repository, or a duplicate operation, exists on a computer other than elsewhere on the web server. When cloning happens, you can edit files in the preferred editor and use Git to track changes without having to stay online. The repository throw that you cloned connects to the remote version so that local changes can be pushed to the remote when you are online

  • Free program

    Free user account settlement solution. Users can collaborate on an infinite number of common warehouses through an infinite number of collaborators.

  • Public warehouse

    The public repository can be viewed by anyone, including people who aren’t GitHub users.

  • Contribution to the public

    Contributions to public (as opposed to private) repositories.

  • keywords

    The specific text used to close an issue when a pull request is made.

  • Write access

    The level of permission on the repository that allows users to push or write changes to the repository.

  • branch

    A branch is a parallel version of a repository. It is included in the repository but does not affect the main or master branch, allowing you to work freely without interrupting the “just-in-time” version. After you have made the required changes, you can merge the branches back into the Master branch to publish the changes.

  • Branch limit

    A restriction that the warehouse administrator can enable to only allow certain users or teams to push to branches or make certain changes.

  • A copy of the

    A GitHub Enterprise instance that provides redundancy for the primary GitHub Enterprise instance.

  • Function branch

    A branch used to try out new features or fix issues that have not been formally used. Also known as subject branching.

  • collaborators

    A collaborator is a person who is invited to participate by the warehouse owner and has read and write permissions on the warehouse.

  • Single sign-on (sso)

    Also known as SSO. Allows the user to log in to one location – the identity provider (IdP) – and then grants the user access to other service providers.

  • card

    A removable box in the project board associated with an issue or pull request.

  • The compression

    Merge multiple submissions into one. Also Git command.

  • Participate in the guide

    Documentation explaining how people should participate in the project

  • In notice

    Notifications of updates to conversations in a pull request when your username or team is mentioned or when you previously responded to comments

  • release

    Github’s way of packaging software and making it available to users

  • Protected branch

    Protected branches prohibit many Git functions on branches chosen by the repository administrator to be protected, must be checked for failure or must be reviewed for approval, and cannot be forced to push, delete, or merge changes

  • rebase

    You reapply a series of changes from one branch to a different base branch and reset the HEAD of the branch to the result

  • Visible team

    Teams that can be viewed and referred to by each organization member

  • merge

    Extracting changes from one branch (in the same repository or from one branch) and then applying them to another branch is usually done as a “pull request” or through the command line. If there are no conflicting changes, the merge can be done using a pull request from the Github.com Web interface, or always from the command line

  • Merge conflicts

    Differences between merged branches, merge conflicts occur when people make different changes to the same line of the same file, or when one person edits a file while another deletes it, and merge conflicts must be resolved before branches can be merged

  • team

    A group of organizational members that reflects the structure of a company or group through cascading access rights and references

  • Team maintainer

    An organization member with part of the organization owner’s team management authority

  • The team plans to

    Provides you with an organizational settlement solution for unlimited public and private warehouses

  • Fence code block

    You can use three back quotes before and after the code block to create the indented code block through the Gtihub Markdown

  • Fixed warehouse

    The warehouse that the user has decided to highlight in his profile

  • Basic authentication

    Authentication method in which credentials are sent as unencrypted text.

  • Basic branch

    The branch that merges changes into when a pull request is merged. When creating pull requests, you can change the base branch from the default branch of the repository to another branch if necessary.

  • After carving

    Forks are personal copies of other user repositories on your account. Forks allow you the freedom to change projects without affecting the original upstream repository. You can also open pull requests in the upstream repository and fork to synchronize the latest changes, since the two repositories are still connected.

  • External collaborator

    A user who has been granted access to the warehouses of one or more organizations but has no other access to the organization and is not a member of the organization.

  • The head branch

    The branch whose changes are merged into the base branch when the pull request is merged, also known as the “comparison branch.”

  • The subgroup

    Within a nested team, inherit the parent team’s access and the sub-teams mentioned by @.

  • The security log

    Lists the logs of the last 50 operations or operations performed in the past 90 days.

  • The instance

    Organizes the GitHub private copies contained in the virtual machines it configures and controls.

  • review

    Review allows others with access to the warehouse to comment on proposed changes in pull requests, approve changes, or request further changes before pull requests are merged.

  • The key fingerprint

    A short series of bytes used to identify a longer public key.

  • The key chain

    A password management system in macOS.

  • Nested team

    The child team of the parent team. You can have multiple sub-teams (or nested teams).

  • differences

    A difference is the difference between a change or saved change between two commits, which visually describes what has been added or removed from the file since the last commit.

  • Saved reply

    You can save and add comments to GitHub user accounts, which can then be used in GitHub issues and pull requests.

  • A personal account has been locked

    A personal account that a user cannot access. The account is locked out when a user demotes their paid account to a free account or their paid plan expires.

  • Billing clerk

    An organization member responsible for managing the organization’s billing setup.

  • Mail the bill

    GitHub organization email address used to send receipts, credit card or PayPal charges and other bill-related communications.

  • Bill recovery token

    The authentication credentials stored as part of the account recovery setup are called “remote Recovery accounts” and are used to store this backup credentials.

  • seats

    Users in the GitHub Enterprise organization are referred to as “seats.”

  • Open source

    Open source software is software that is freely available for anyone to use, modify, and share (in modified and unmodified form). Today, the concept of “open source” often extends beyond software, representing a collaborative principle in which working materials are available online for anyone to fork, modify, discuss, and participate in.

  • Remote Account Recovery

    Allows users to add an extra layer of security to their GitHub account when two-factor authentication methods or recovery code are unavailable. Users can associate their GitHub account with their Facebook account by storing their GitHub account authentication credentials in the form of an account recovery token via Facebook.

  • Forced to push

    A Git push that uses local changes to override remote repositories, regardless of conflict

  • Must pull request review

    A collaborator can change a protected branch only after a review is required to ensure that the pull request has received at least one approval review.

  • Required status check

    Pull request checks to ensure that all necessary CI tests have passed before collaborators can make changes to the protected branch.

  • The snapshot

    The checkpoint of the VIRTUAL machine at a point in time.

  • Fast forward

    Fast forward is a special type of merge in which you have revisions as well as “merge” changes to another branch as children of an existing branch. In this case, you cannot make a new merge commit, but just update the revision. This often happens in the remote trace branch of a remote repository.

  • Return code

    Code to help you regain access to your GitHub account.

  • Members of the figure

    Displays a warehouse diagram of all branches of the warehouse.

  • The owner of the

    An organization member who has full management rights for the organization.

  • Clock in figure

    A warehouse chart showing the frequency of warehouse updates by weekly date and time

  • pull

    Pull refers to extracting and merging changes. For example, if someone edits a remote file that you operate on, you pull those changes to a local copy to keep it up to date. See also “Extraction”.

  • Pull permissions

    Synonym for read permission.

  • The pull request

    A pull request is a proposal to change a user-submitted repository, which is then accepted or rejected by the repository collaborator. Like issues, each pull request has its own forum.

  • Pull request review

    Comments in a pull request where a collaborator approves changes or requests further changes before the pull request is merged.

  • Continuous integration

    Also called CI. Run automated build and test processes after individuals commit changes to the repository configured on GitHub. CI is a common best practice in software development to help detect errors.

  • hook

    Annotate optional scripts to allow developers to add features or check when multiple Git commands are executing normally. In general, hooks allow pre-validation and potential abort commands, and post notification after the operation is complete.

  • push

    Push means sending committed changes to a remote repository on GitHub.com. For example, if you change content locally, you can push those changes for others to access.

  • Push the branch

    After successfully pushing the branch to the remote repository, you can update the remote branch by changing the local branch. When you push a branch, Git searches the remote repository for the branch’s HEAD ref and verifies that it is the direct source of the branch’s local HEAD ref. After validation, Git pulls all objects (reachable from the local HEAD ref, missing from the remote repository) to the remote object database, and updates the remote HEAD ref. If the remote HEAD is not the source of the local HEAD, the push fails.

  • Push permissions

    A synonym for write permission

  • submit

    A submission or “revision” is an individual change to a document (or group of documents). When you commit to save work, Git creates a unique ID (also known as “SHA” or “hash”) that keeps track of the specific changes committed and who committed them and when. Commits typically contain a commit message that briefly explains the changes made.

  • Submit ID

    Also called SHA. A 40-character checksum hash used to identify submissions.

  • Submit the author

    The user making the submission.

  • Submit figure

    Displays all warehouse maps submitted for the warehouse in the past year.

  • Commit message

    A short descriptive text accompanying the submission to communicate the changes introduced by the submission.

  • mention

    A notification sent to a user by prefacing the user name with the @ symbol. Users in organizations on GitHub can also be part of a mentioned team.

  • schedule

    A series of events in a pull request or user profile.

  • star

    Warehouse of bookmarks or appreciation expressed. Stars are a manual way to rank projects in popularity.

  • Temporary instance

    A way to test changes before they are applied to an actual GitHub Enterprise instance.

  • Service link

    Also known as “Web hooking.” A Web hook is a notification method that sends notifications to an external Web server whenever a specific operation occurs on a repository or organization.

  • Confidential team

    A team that is visible only to the rest of the team and to people with owner rights.

  • To view

    You can follow the repository or issues to be notified when there are updates to issues or pull requests.

  • Check the notification

    Notifications about activities in the repository to which the user subscribes.

  • The label

    Issue or pull request flag. The repository comes with a set of default tags, but users can also create custom tags.

  • tag

    A system for annotating and formatting documents.

  • Root file system

    Basic operating system and GitHub Enterprise application environment.

  • The root directory

    The first directory in the hierarchy

  • Check out the

    You can use Git checkout on the command line to create a new branch, change your current working branch to a different branch, or even switch from a different branch to a different version of a file using Git checkout [branchname] [path to file]. A check-out operation updates all or part of the working tree, as well as the index and HEAD (if the whole working tree points to a new branch) using a tree object or BLOB from the object database.

  • check

    A check is a status check on GitHub

  • Compare the branch

    Branches used to create pull requests. This branch is compared to the base branch that you chose to use to pull the request and determine the changes. When a pull request is merged, the base branch is updated with the changes made to the comparison branch. Also called the “head branch” of a pull request.

  • Permanent link

    A permanent static hyperlink to a specific web page.

  • News feed

    An active view of the warehouse or people you care about. An organization’s message feed shows activity on an organization-owned warehouse.

  • clean

    The working tree is clean if it corresponds to the version of the current HEAD reference. See also “dirty”.

  • The source

    Default upstream repository. Most projects have at least one upstream project that they track. By default, the source is used for this purpose.

  • The parent team

    Within a nested team, the sub-team is passed its access and the primary team referred to by @

  • state

    A visual representation in a pull request that indicates that your submission meets the conditions set by the repository you participate in.

  • State examination (mmse)

    Status checks are external processes, such as continuous integration builds, that run for every commit you make in the repository. See “About Status Checking” for more information.

  • Production branch

    Branches that contain final changes that can be used or deployed to an application or site.

  • The user

    The user is a person with a personal GitHub account. Each user has a profile and can have multiple repositories (public or private). They can create or be invited to join an organization or collaborate with other users in a repository.

  • The user name

    The user’s handle on GitHub.

  • Email notification

    Notifications sent to the user’s E-mail address.

  • Private warehouses

    A private repository is visible only to the repository owner and owner-designated collaborators.

  • Private contributions

    Contributions to private (as opposed to public) repositories.

  • Management console

    The part of the GitHub Enterprise interface that contains administrative capabilities.

  • organization

    An organization is a group of two or more users, usually corresponding to the actual organization. They are managed by users and can contain warehouses and teams.

  • Organization owner

    Users who have full administrative rights over their own organizations.

  • The settlement cycle

    The time interval for a particular settlement scheme.

  • Settlement scheme

    Payment schemes for users and organizations, including capabilities set for each scheme type.

  • Network diagram

    A warehouse diagram that shows a branch history for the entire warehouse network, including branches of the root warehouse as well as branches that contain forks unique to the network.

  • Pulse diagram

    A warehouse map that provides a summary of warehouse activities.

  • dirty

    The working tree is considered dirty if it contains changes that have not been committed to the current branch.

  • Readme file

    A text file that contains information about files in the repository and is usually the first file seen by a visitor to the repository. The readme document, along with warehouse licenses, participation guidelines, and codes of conduct, helps you communicate requirements and manage project participation.

  • To obtain

    When you use Git Fetch, you add changes from a remote repository to a local work branch without committing them. Unlike Git pull, extraction lets you review changes before they are committed to a local branch.

  • Code of conduct

    Documentation that sets standards for how to participate in the community.

  • Comment line

    Pull comments on specific lines of code within the request.

  • Line end

    A symbol representing an invisible character at the end of a line in a text file.

  • To solve

    A symbol representing an invisible character at the end of a line in a text file.

  • Schedule a task

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

  • To subscribe to

    GitHub plans for users or organizations.

  • issue

    Topics are proposed improvements, tasks, or issues related to the warehouse. Anyone can create an issue (for a common warehouse), which can then be mediated by the warehouse collaborator. Each topic has its own discussion thread. You can also use tags to group topics and assign them to someone.

  • The license

    A document that accompanies a project that tells you what you can and cannot do with your source code.

  • equipment

    A software application that combines an appropriate operating system (JeOS) to run optimally on industry-standard hardware (usually a server) or in a virtual machine.

  • The access token

    A token used in place of a password when performing Git operations over HTTPS on the command line or API, also known as a personal access token.

  • diagnosis

    An overview of GitHub Enterprise instance setup and environment.

  • Read permissions

    The level of access to the repository that allows users to pull and read information from the repository. All public repositories grant read permissions to all GitHub users. Synonym for pull permissions.

  • contribution

    Specific events on GitHub will: – Add squares to user’s contribution graph: “Recorded as contributed activities” – Add activities to user profile timeline: “Contributed activities”

  • Contribution figure

    The portion of a user’s profile that shows his or her participation history (up to one year, displayed by day).

  • contributors

    Contributors are people who do not have collaborator rights to the repository but have worked on the project and their open pull requests have been consolidated into the repository.

  • Follow up (users)

    Get notifications about another user’s contributions and activities.

  • Identity provider

    Also known as IdP, is a trusted provider that lets you access other web sites using SAML single sign-on (SSO).

  • The transfer

    Transferring a warehouse means changing the owner of the warehouse. The new owner can immediately manage the repository’s content, issues, pull requests, releases, and Settings.

  • reduction

    When a pull request is resumed on GitHub, a new pull request is automatically opened with a commit to recover the merge commit from the original merge pull request. In Git, you can use Git Revert to restore a commit.

  • The remote

    This is a repository or branch version hosted on a server (most likely GitHub.com). Remote versions can connect to local clones to keep changes in sync.

  • The remoteURL

    Where to store code: GitHub, other user branches, or even repositories on different servers.

  • Remote warehouse

    A warehouse used to track the same project but stored in another location.

  • trace

    The “trace” feature in Git describes the most recent changes made to each line of a file, typically showing the revision, author, and when. This is useful, for example, to keep track of when functionality was added or which commit caused a particular vulnerability.

  • Traffic diagram, traffic diagram

    A warehouse map showing warehouse traffic, including full clones (not extracts), visitors for the last 14 days, recommended sites, and popular content.

  • notice

    Updates delivered on the Web or by E-mail (depending on your Settings) that provide information about the activities you are interested in.

  • The deployment of key

    The deployment key is an SSH key stored on the server that is granted access to a single GitHub repository. This key is attached directly to the repository rather than the individual user account.

  • milestone

    A way of tracking the progress of issues in the warehouse or pulling groups of requests.

  • The mirror

    A new copy of the warehouse.

  • stop

    Used to remove the ability for users to work collaboratively on an organizational repository.

  • integration

    A third-party application that integrates with GitHub, be it a GitHub application, an OAuth application, or a Web hook.

  • The cluster

    Run the GitHub Enterprise service on multiple nodes to load balance requests between nodes

  • The fast forward

    When the local copy of the repository is not synchronized with the upstream repository, you need to extract the upstream changes before pushing the local changes.

  • The project board

    A GitHub board composed of issues, pull requests, and comments, classified by column as cards.

  • Prereceive hook

    Scripts that run on GitHub Enterprise servers that can be used to perform quality checks.

  • Verification code

    You provide a code in addition to the GitHub password when using 2FA to log in through a browser. This code is generated by the app or sent to the phone via SMS, also known as a “2FA verification code”.

  • High availability

    A system or component that continues to run for the required length of time.

  • The default branch

    A basic branch of the repository for new pull requests and code submissions. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called “main” and is usually the default branch.

  • The default image

    An automatically generated image that is used as the default profile picture when users sign up for GitHub. Users can replace their avatars with photos of themselves.