The following terms are often used in documentation, blog posts, and everyday life at GitLab. This list is always a work in progress and additions are very welcome. When adding or editing an entry, please do not have the headers be clickable hyperlinks as this seems to break the TOC functionality (i.e. clicking on the item in the TOC will go to the external hyperlink instead of the deep link).
The oversight, development, and maintenance of computer programs. Gitlab has advantages over both legacy and modern ALM tools.
Independent line of development. New commits are recorded in the history of the branch you are working in.
The ability to initiate an action from chat.
Bots that run in your chat application and give you the ability to do "anything" from chat.
a local copy of the project you want to work on.
Introduction to ConvDev: https://about.gitlab.com/2016/09/14/gitlab-live-event-recap/
A natural evolution of software development that carries a conversation across functional groups throughout the development process, enabling developers to track the full path of development in a cohesive and intuitive way. ConvDev accelerates the development lifecycle by fostering collaboration and knowledge sharing from idea to production.
A process that involves adding new code commits to source code with the combined code being run on an automated test to ensure that the changes do not break the software. Thoughtworks discusses continuous integration.
Continuous deployment is the next step of continuous delivery: Every change that passes the automated tests is deployed to production automatically. The difference between Continuous Delivery and Continuous Integration.
Continuous delivery is a series of practices designed to ensure that code can be rapidly and safely deployed to production by delivering every change to a production-like environment and ensuring business applications and services function as expected through rigorous automated testing.Amazon moves toward continuous delivery
The time it takes to move from idea to production.
As in "specify dependencies between stages"
The epicenter of software engineering, quality assurance, and technology operations. DevOps glossary by XebiaLabs.
A commit that shows the changes before and after.
A folder used for storing multiple files.
Related blog post: https://about.gitlab.com/2016/05/23/gitlab-container-registry/
External reference: https://www.masteringemacs.org/article/mastering-key-bindings-emacs
A copy of an original repository that you can put somewhere else or where you can experiment and apply changes that you can later decide if publishing or not, without affecting your original project.
External reference: Blog post
TOFU: top of funnel MOFU: middle of funnel BOFU: bottom of funnel
Also see the main Git project.
External reference: https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks
From the page that is linked in the title: "Git has a way to fire off custom scripts when certain important actions occur. There are two groups of these hooks: client-side and server-side. Client-side hooks are triggered by operations such as committing and merging, while server-side hooks run on network operations such as receiving pushed commits."
Difference between a webhook and a git hook: a git hook is local to its repo (usually) while a webhook is not (it can make API or http calls). So for example if you want your linter to fire before you commit, you can set that up with a git hook. If the linter fails, the commit does not go through. A git hook can be configured to go beyond its repo, e.g. by having it make an API call.
External reference: https://git-scm.com/docs/git-gui
Git command to synchronize the local repository with the remote repository, by fetching all remote changes and merging them into the local repository. ("git pull origin [branch name]")
Git command to send commits from the local repository to the remote repository.
Modified files that have been marked to go into the next commit.
New files that Git has not been told to track previously. Add them by using the command "git add [file path]"
Files that have been modified but are not committed. Check them by using the command "git status"
See GitLab Geo documentation
Related blog post: https://about.gitlab.com/2016/09/13/gitlab-master-plan/.
See GitLab Pages description.
Related project: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner
External reference: https://gogs.io/
Related blog post
The use of open source development techniques within the corporation.
External reference: http://www.irchelp.org/
Static code analysis for our various file types. For example, we use scss-lint to ensure that a consistent code styling is respected. Similar tools: rubocop / eslint.
Takes changes from one branch, and applies them into another branch.
External reference: https://en.wikipedia.org/wiki/Mount_(Unix)
As stated on the wikipedia page, "Mounting makes file systems, files, directories, devices and special files available for use and available to the user."
For example, we have NFS servers where the git files reside. In order for a worker node to "see" or "use" the git files, the NFS server needs to be mounted on the worker; that is, the worker needs to know that the NFS server exists and how to connect to it. Think of it as getting a shared drive to show up in your Finder (on Mac) or Explorer (on Windows).
On your own server. The fact that GitLab is on premise is a strong point for large corporate clients concerned with security.
External reference: https://en.wikipedia.org/wiki/Open_core
GitLab's business model. Coined by Andrew Lampitt in 2008, the open core model primarily involves offering a "core" or feature-limited version of a software product as free and open-source software, while offering "commercial" versions or add-ons as proprietary software.
External reference: https://opensource.org/docs/osd
Including to providing access to the source code, open source software must comply with a number of criteria, among them free distribution and no discrimination against persons, groups, or fields of endeavor.
Related blog post: https://about.gitlab.com/2016/01/11/being-a-good-open-source-steward/
A regression is something that used to work one way in the last release and then we made a breaking change and it no longer works the same way.
A regression is defined as a change that results in a negative impact on the functionality of an existing feature due to recent changes, i.e. the latest release.
A directory where Git has been initialized to start version controlling your files. The history of your work is stored here.
Related blog post: https://about.gitlab.com/2015/05/18/simple-words-for-a-gitlab-newbie/
A repository that is not-on-your-machine, so it's anything that is not your computer. Usually, it is online, GitLab.com for instance. The main remote repository is usually called “Origin”.
Related documentation: https://docs.gitlab.com/ce/gitlab-basics/start-using-git.html
Terminal on Mac OSX, GitBash on Windows, or Linux Terminal on Linux
Documentation on creating your own SSH key A unique identifier of a computer. It is used to identify computers without the need for a password. e.g. On GitLab I have added the ssh key of all my work machines so that the GitLab instance knows that it can accept code pushes and pulls from this trusted machines whose keys I have added.
External definition: https://wiki.python.org/moin/StaticSiteGenerator
External definition: http://whatis.techtarget.com/definition/multi-tenancy
A multi-tenant GitLab instance can have any number of customers - such as companies or groups of users using it. GitLab.com is an example of a multi-tenant GitLab instance.
External definition: http://searchcloudapplications.techtarget.com/definition/single-tenancy
A single-tenant GitLab instance has only one customer - such as a company - using it. On premise GitLab instances are almost exclusively single-tenant.
External conversation: https://news.ycombinator.com/item?id=12487112
Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later.
Copying files into another directory on your local computer. This is a common and early form of version control, but it is error-prone.
These systems, such as CVS, Subversion, and Perforce, have a single server that contains all the versioned files, and a number of clients that check out files from that central place. For many years, this has been the standard for version control.
External reference: https://en.wikipedia.org/wiki/Distributed_version_control
Distributed version control, also known as distributed revision control or decentralized version control, allows many software developers to work on a given project without requiring them to share a common network.
DVCSs fully mirror the repository. Git, Mercurial, Bazaar, and Darcs are DVCSs. If any server dies, and these systems were collaborating via it, any of the client repositories can be copied back up to the server to restore it.
External reference: https://cloud.google.com/compute/docs/instances/
A way for for an app to provide other applications with real-time information e.g. send a message to a slack channel when a commit is pushed