Granular user roles and flexible permissions

Manage access and permissions with five different user roles and settings for external users. Set permissions according to people’s role, rather than either read or write access to a repository. Don’t share the source code with people that only need access to the issue tracker.

Protected tags

Granular permissions for tags you want to protect.

Access to the server

You have complete control of the server/instance, so you can install additional software (intrusion detection, performance monitoring, etc.) and view log files on the server itself. GitLab’s advanced log system means everything gets logged and provides you with easy access to a wealth of log file information.

AD / LDAP integration

Sync groups, manage SSH-keys, manage permissions, authentication and more. You can manage an entire GitLab instance through the LDAP / AD integration.

Multiple LDAP / AD server support

Link multiple LDAP servers to GitLab for authentication and authorization

Create and remove admins based on an LDAP group

Use LDAP groups to create or remove admins from your GitLab instance.

Kerberos user authentication

Authenticate users with Kerberos.

Multiple LDAP server support (compatible with AD)

Integrate with multiple LDAP servers for use when authenticating users.

LDAP group sync

GitLab Enterprise Edition gives your Admin’s the ability to automatically sync groups and manage SSH-keys, permissions, and authentication, so you can focus on building your product, not configuring your tools.

LDAP group sync filters

GitLab Enterprise Edition Premium gives more flexibility to synchronize with LDAP based on filters, meaning you can leverage LDAP attributes to map GitLab permissions.

Multiple integrations

GitLab can integrate with Authentication and Authorization (LDAP / AD) mechanisms, multiple 3rd party services, CI/CD, and other tools such as ALM, PLM, Agile and Automation tools.

Application Partners

Since every application that supports Git will work with GitLab, there are hundreds of applications that can integrate and work with Gitlab. Additionally, there are many partners that integrate with authentication and authorization of GitLab.

Various authentication mechanisms

GitLab can integrate with most of the authentication and authorization providers.

Free Guest users

Guest users don’t count towards the license count.

Enforce accepting terms of service

Enforce your users accepting new terms of service by blocking GitLab traffic.

SAML SSO for Groups

Connect a group in GitLab to a SAML identity provider to manage authentication.

Allow SAML assurance level to bypass 2FA

it is now possible to honor the SAML provider’s assurance level, allowing to disable the two-factor authentification on GitLab side via a new SAML configuration option

Enforced Two-factor Authentication (2FA)

Two-factor authentication secures your account by requiring a second confirmation, in addition to your password. That second step means your account stays secure even if your password is compromised. The ability to enforce 2FA provides further security by making sure all users are using it.

Smart card support

Authenticate into GitLab using a smart card with a compliant X.509 certificate.

IP Whitelisting

IP Whitelisting defines safe IP network addresses from which clients can access and interact with the repository server. This helps prevent unwanted third parties from accessing your account even if they have acquired a team member’s email address and password.

Custom header and footer system message in web and email

Include custom header and footer system messages throughout GitLab and in emails.

Issues

Quickly set the status, assignee or milestone for multiple issues at the same time or easily filter them on any properties. See milestones and issues across projects.

Description Templates

By adding a description template to your issues or merge requests, users who create a new issue or merge request can select a template to help them to communicate effectively.

Task Lists

Use task lists in issues, merge requests, and epics to manage tasks and track their completion using checkboxes.

File Attachments

Upload file attachments (including images) to issues, merge requests, and epics, to communicate ideas beyond text.

Award Emoji

Award emoji in issues, merge requests, and epics, for more expressive communications, and to indicate upvotes and downvotes.

GitLab Flavored Markdown

GitLab uses ‘GitLab Flavored Markdown’ (GFM). It extends the standard Markdown in a few significant ways to add some useful functionality.

Threaded Discussions

Collaborate with threaded discussions in issues, merge requests, and epics.

Filterable System Activity

View system activity to see a history of changes to issues, merge requests, and epics. Filter by comments only or history only.

Track Title Changes

Track title changes in the system activity of issues, merge requests, and epics.

Labels

Labels provide an easy way to categorize issues, merge requests, or epics based on descriptive titles as ‘bug’, or ‘documentation’.

Prioritized Labels

Assign prioritized labels with issues and merge requests to display them in priority order.

Issue Weights

GitLab lets you manage issues using Agile practices by setting the weight of an issue.

Milestones

Create and manage milestones at both the project and group levels, viewing all the issues for the milestone you’re currently working on, representing an Agile sprint or a release.

Issue Due Dates

In GitLab, you can set a due date for individual issues. This is very convenient if you have small tasks with a specific deadline.

Assignee

Assign a user to an issue or a merge request, indicating responsibility for it.

Multiple Issue Assignees

Assign more than one person to an issue at a time.

Lock Discussion

Lock down continued discussion in an issue or merge request as a Master role or higher, to prevent further abuse, spam, or unproductive collaboration.

Confidential Issues

Keep your information secure with Confidential Issues. With GitLab, you can create confidential issues visible only for project members with Reporter access level or above.

Related Issues

Explicitly mark issues as related and track their status.

Move Issue to Another Project

You can move issues between projects in GitLab. All links, history and comments will be copied and the original issue will reference the newly moved issue. This makes working with multiple issue trackers much easier.

Mark Issue as Duplicate

Mark an issue as a duplicate of another issue, closing it.

Anticipate Duplicate Issue

When creating a new issue, see similar existing issues, to reduce the number of duplicates and focus collaboration.

New Issue via Email

Create an issue from email by sending in the issue title and description.

Bulk Edit

Edit multiple issues or merge requests all at once.

Export Issues CSV file

Issues can be exported as CSV from GitLab and are sent to your default notification email as an attachment.

Import Issues CSV file

Issues can be imported from a CSV into GitLab, generated from another issue tracking system.

Burndown Charts

GitLab provides Burndown Charts as part of Milestones. This allows users to better track progress during a sprint or while working on a new version of their software.

Issue Analytics

See issue analytics at the group level.

Quick Actions

GitLab provides a convenient way to change metadata of an issue or merge request without leaving the comment field with quick actions.

Custom Notifications

Be notified by email, Slack, or ToDos anytime there are changes to an issue or merge request.

Todos

When a user is mentioned in or assigned to an issue or merge request it will be included in the user Todos, making the development workflow faster and easier to track.

Custom Text in Emails

Include custom additional text in all emails sent by GitLab, such as including disclaimer text.

Sub-addressing Email Servers

For incoming email features in GitLab, support sub-addressing email servers.

Catch-all Email Mailboxes

For incoming email features in GitLab, support catch-all email mailboxes, which can be used with Microsoft Exchange and Google Groups.

Jira Integration

To ensure that developers in GitLab and project managers in JIRA remain in tune, GitLab integrates with JIRA and provides the necessary tooling to fill that gap.

Jira Issues Integration

Integrate Jira issues with GitLab merge requests.

Jira Development Panel Integration

View GitLab repository information and navigate to GitLab from the JIRA development panel.

Track Description Changes

View the full history of description updates in issues, merge requests, and epics.

Track Comment Changes

View the full history of comment updates.

Drag and Drop Tasks

Drag and drop tasks in a task lists.

Rich Object Summary on Link Hover

View an information-rich summary by hovering over links to users, issues, merge requests, and other objects in GitLab.

Create GitLab Branch from Jira Development Panel

Create a GitLab branch from within the development panel of a JIRA issue.

Create GitLab Merge Request from Jira Development Panel

Create a GitLab merge request from within the development panel of a JIRA issue.

Project Financial Management

Tracking, managing and reporting on the budget and actual costs of the project. Able to allocate costs to OPex or CAPex depending on specific organization reporting rules. Time tracking information used to determine labor cost allocations. Specific features would include: budget, spend, time tracking, resource cost, Capex/Opex.

Project Issue Board

GitLab has Issue Boards, each list of an Issue Board is based on a label that exists in your issue tracker. The Issue Board will therefore match the state of your issue tracker in a user-friendly way.

Group Issue Board

Issue board scoped at the group level, so that you can view issues in all projects of that group.

Multiple Project Issue Boards

Large companies often have hundreds of different projects, all with different moving parts at the same time. GitLab Enterprise Edition allows for multiple Issue Boards for a single project so you can to plan, organize, and visualize a workflow for a feature or product release. Multiple Issue Boards are particularly useful for large projects with more than one team or in situations where a repository is used to host the code of multiple products.

Multiple Group Issue Boards

Multiple Group Issue Boards, similar to Multiple Project Issue Boards

Total Issue Count per Issue Board List

View the total number of issues in an issue board list, at the top of the list.

Total Issue Weight per Issue Board List

View the total weight of issues in an issue board list, at the top of the list.

Issue Board Label Lists

An Issue Board is based on its project’s label structure, therefore, it applies the same descriptive labels to indicate placement on the board. GitLab issues can appear on multiple issues and they still have meaning without the context of a particular board.

Issue Board Assignee Lists

Issue board lists that pull in issues assigned to a given user

Issue Board Milestone Lists

Issue board lists that pull in issues in a given milestone

Issue Board Configuration

Associate a board with a milestone, labels, an assignee, and a weight

Issue Board Focus Mode

Get more information at a time with the Issue Board focus mode, which removes all unnecessary elements from the screen to show your Issue Boards.

Reorder Issues in Issue Board List

Reorder issues in an issue board list to indicate priority and intended order of implementation.

Add Multiple Issues to Project Issue Board

From an Issue Board, you can add multiple issues to lists in the board by selecting one or more existing issues.

New Issue in Issue Board List

With GitLab Issue Boards, you can create issues directly from the board and assign multiple labels allowing them to appear on multiple boards.

Issue Board Epic Swimlanes

View epics as swimlanes in an issue board.

Issue Board with Custom Workflows

An issue board pre-configured with a custom workflow.

Issue Board Types

Issue boards/dashboards reflect an organizations flow for processing work items. These boards can reflect individualized workflow or follow established patterns. Issue board types with established patterns (such as Scrum and Kanban) can make setup of new boards easier.

Issue Board Configuration with Advanced Logic

Define what issues show in an issue board using advanced Boolean logic.

Time Tracking

Time Tracking in GitLab lets your team add estimates and record time spent on issues and merge requests.

Track Time Spent

Update and track the time spent on an issue or merge request.

Track Estimated Time Required

Update and track the estimated time required on an issue or merge request.

Advanced Time Tracking

Able to capture individual time reporting for specific assigned tasks and then to allocate labor costs to the appropriate project. Specific features would include: estimate, actual, cost, reporting.

Multi-level Epics

Plan and track strategies, initiatives, and features with multi-level epics that collect issues together.

Reorder Issues in Epic

Reorder issues in an epic to indicate priority or intended order of implementation.

Epic Fixed Dates

Use fixed dates to do top-down planning of epics.

Epic Dynamic Dates

Use dynamic dates to do bottoms-up planning and tracking of epics, taking into account of dates of children.

Promote Issue to Epic

Promote an issue to epic to continue collaboration at a higher-level work abstraction.

Roadmaps

Visualize multiple epics across time in a roadmap view.

Backlog Management

Able to capture and track future features, capabilities, and work in a consolodated and organized list which enables the team to organize, prioritize, accept, plan and start work on relevant items. The backlog is where future work is captured, defined, evaluated, and planned. Specific features would include: Backlog, user stories, issues, effort estimate, priority, backlog board.

Risk/Issue Management

Able to define and manage project RISK and ISSUE status and workflow to identify, track, mitigate and resolve potential risks and active issues facing the project. Risk/Issue status and resolution managed through online workfow that tracks assignment and actions to address the specific item. Specific features would include: workflow, risk severity, risk priority, Assigning Risk/Issue for action, Risk/Issue status.

DevOps Pipeline

Able to establish visibility into the end to end DevOps pipeline so the entire team is aware of pipeline status and can contribute to overall success. Specific features would include: visibility into status of pipeline

Portfolio Planning

Establishing strategic priorities and direction in order to govern the allocation of corporate resources to support specific business/IT initiatives. Strategic planning evaluates in-flight projects and proposed future initiatives to shape and govern the ongoing investment in projects and discretionary work. Able to model and optimize different portfolio investment scenarios to determine the ideal funding combinations to meet strategic priorities. Specific features would include: Proposals, epics, backlog, strategic alignment, estimation, prioritization, what-if, monte-carlo simulation, optimization.

Portfolio Status Management

Tracks and reports on the overall status and health (scope, schedule, budget) of projects and programs within the portfolio to enable executives to support project execution. Specific features would include: forecasting, status tracking, release planning, roadmap, milestones, project/program hierarchy.

Scrum

Able to support the time-boxed (sprint) approach of the Agile -Scrum software delivery. Specific features would include: Issues, scrum boards, burndown charts, burn up.

Kanban

Able to support the flow based approach of Agile - Kanban software delivery. Specific features would include: Issues, Kanban boards, burn up, cumulative flow diagram.

SAFe (Scaled Agile Framework) - Essential SAFe

Able to support the key principles and practices of the Essential SAFe configuration., Agile Release Train, (a combined CD pipeline where multiple projects align to release), Planning Increment (PI) Planning (cadence driven project planning/ vision)

SAFe (Scaled Agile Framework) - Lean Portfolio Management

Provides support for the key elements of Lean Portfolio Management. Specific features would include: Release Train, Lean Portfolio Management.

Issue Board Epic Swimlanes

View epics as swimlanes in an issue board.

Financial Management

Tracking, managing and reporting on the budget and actual spend of projects and programs within specific portfolios. Able to allocate costs to OPex or CAPex depending on specific organization reporting rules. Time tracking information used to determine labor cost allocations. Specific features would include: budget, spend, time, resource cost.

Resource/Team Management

Tracks and manages the availability of team members by skill, experience, location, and cost, so they can support both planned and unplanned work. Specific features would include: individual capacity, individual skills, individual assignments, labor cost.

Work Planning/Management

Able to define, schedule and assign specific tasks to team members and manage the sequence and interdependency of tasks with each other. This form of structured planning is needed when tasks are clearly defined and sequence of execution is critical. Specific features would include: WBS, Gantt Chart, Task Assignment, Scheduling, task sequence, task relationships.

Out-of-the-box Agile Reporting

Teams have access to more than a dozen out-of-the-box reports with real-time, actionable insights into how their team is performing sprint over sprint. Example reports are sprint burndown, epic burndown, cumulative flow diagram, velocity chart, burn up chart, and sprint report.

Product Roadmap

Establishing the product vision and strategy to organize, govern and shape the effort of the multi-disciplinary team building specific business services. The Product Roadmap is based on specific business goals and objectives, manages high level requirements, prioritizes future features, allocates resources, tracks progress and measures business results linked to the business strategy. Specific features would include: Product Strategy, Idea Gathering, Requirements Management, Resource Management, Feedback Collection, Milestone Tracking, Release Management, Workflow Management, Feature Tracking/Deviation, Roadmap Analytics, Centralized Notes, Report Generation, Imports, API/SDK, Conflict Management, and Customized Alerting.

Value Stream Management

GitLab will surface VSM (value stream management) style metrics, such as cycle time, lead time, and deployment frequency, aggregated and rolled up, per an individual team, across multiple teams within a department, or even across the entire organization.

Requirements Management

Able to gather, document, refine and track approval of business and system requirements. Managing and tracking the relationships between requirements and other requirements, requirements and code, requirements and test cases for each version of requirements. Specific features would include: definition, traceability, requirement hierarchy, dependency.

Quality Management

Able to support test planning, definition of test cases, results of test execution and corresponding backlog of work resulting from failed tests. Specific features would include: Test case planning, test execution, defect tracking (backlog), severity, priority.

Service Desk

Allow external users to create issues in your GitLab instance without an account and without access to anything except their issue. Manage tickets from the GitLab interface.

Service Desk via Web

Access Service Desk via a web form, in addition to email.

Commit graph and reporting tools

GitLab provides commit graphs and reporting tools about collaborators’ work.

Description Templates

By adding a description template to your issues or merge requests, users who create a new issue or merge request can select a template to help them to communicate effectively.

Task Lists

Use task lists in issues, merge requests, and epics to manage tasks and track their completion using checkboxes.

File Attachments

Upload file attachments (including images) to issues, merge requests, and epics, to communicate ideas beyond text.

Award Emoji

Award emoji in issues, merge requests, and epics, for more expressive communications, and to indicate upvotes and downvotes.

GitLab Flavored Markdown

GitLab uses ‘GitLab Flavored Markdown’ (GFM). It extends the standard Markdown in a few significant ways to add some useful functionality.

Threaded Discussions

Collaborate with threaded discussions in issues, merge requests, and epics.

Filterable System Activity

View system activity to see a history of changes to issues, merge requests, and epics. Filter by comments only or history only.

Track Title Changes

Track title changes in the system activity of issues, merge requests, and epics.

Lock Discussion

Lock down continued discussion in an issue or merge request as a Master role or higher, to prevent further abuse, spam, or unproductive collaboration.

Quick Actions

GitLab provides a convenient way to change metadata of an issue or merge request without leaving the comment field with quick actions.

Custom Notifications

Be notified by email, Slack, or ToDos anytime there are changes to an issue or merge request.

Todos

When a user is mentioned in or assigned to an issue or merge request it will be included in the user Todos, making the development workflow faster and easier to track.

Jira Integration

To ensure that developers in GitLab and project managers in JIRA remain in tune, GitLab integrates with JIRA and provides the necessary tooling to fill that gap.

Jira Issues Integration

Integrate Jira issues with GitLab merge requests.

Jira Development Panel Integration

View GitLab repository information and navigate to GitLab from the JIRA development panel.

Search files with fuzzy file finder

GitLab provides a way to search a file in your repository in one keystroke.

Fast-forward merge with option to rebase

With this setting at the project level, you can ensure that no merge commits are created and all merges are fast-forwarded. When a fast-forward merge is not possible, the user is given the option to rebase.

Squash and merge

Combine commits into one so that main branch has a simpler to follow and revert history.

Merge approvals

When a project requires multiple sign-offs, GitLab Enterprise Edition enables you to make sure every merge request is approved by one or more people. Merge request approvals allow you to set the number of necessary approvals and predefine a list of approvers that will need to approve every merge request in a project, and in-turn improve your code’s quality.

Merge Requests

Create merge requests and @mention team members to review and safely merge your changes.

Merge conflict resolution

Preview merge conflicts in the GitLab UI and tell Git which version to use.

File Locking

Working with multiple people on the same file can be a risk. Conflicts when merging a non-text file are hard to overcome and will require a lot of manual work to resolve. With GitLab Enterprise Edition Premium, File Locking helps you avoid merge conflicts and better manage your binary files by preventing everyone, except you, from modifying a specific file or entire directory.

Revert specific commits or a merge request from the UI

Revert any commit or a single merge request from GitLab’s UI, with a click of a button.

Powerful branching

A branch in Git contains the entire history that preceds it. It’s also created or moved towards instantly and easily shared.

Protected branches

Granular permissions for branches you want to protect.

Cherry-picking changes

Cherry-pick any commit in the UI by simply clicking the Cherry-Pick button in a merged merge request or a specific commit.

Activity Stream

View a list of the latest commits, merges, comments, and team members on your project.

Publish static websites for free with GitLab Pages

GitLab Pages provides an easy system for hosting static sites using GitLab repositories and GitLab CI, complete with custom domains, access control, and HTTPS support.

Automatically close issue(s) when a merge request is merged

With GitLab, you can use specific keywords to close one or more issues as soon as a merge request is merged.

Restrict push and merge access to certain users

Extend the base functionality of protected branches and choose which users can push or merge to a protected branch.

Built-in and custom project templates

When creating a new project, you can choose to kickstart your project from a predefined template that already has some working example code and CI preconfigured. In addition, you can define a custom project templates by assigning a group. Child projects of this group are available as templates when creating a new project.

Groups dropdown in navigation

Searching for a group is directly available behind a lightweight dropdown menu, removing the need to navigate away from your work into a separate view when you’re looking for a hard-to-remember group.

Initialize README on project creation

A repository can be initialized with an example README when creating a new project. If this option is checked, a project repository is initialized with a default master branch which can be cloned right away.

Manage third party offers

GitLab 11.1 introduces the ability to control the display of third party offers in the administration area, providing more control over the display of these offers

User status message

Define and show your personal status message via an Emoji and text message, exposed on your profile page and on any comment and author line.

Private profile page

In certain situations, when privacy is of concern, users might not want to show their activity, contributions and personal projects. Activity-related information can be disabled in the profile settings.

Download single repository files

When browsing through project repositories on GitLab, having direct access to single files is a relevant use case. A ‘Download’ button in the file viewer allows you to download individual files from the GitLab UI.

Repository languages on project overview

A code languages bar on the project overview shows all relevant languages the GitLab repository consists of, including relative quantity.

Merge request reviews

Draft multiple comments in a merge request code review, before reviewing and submitting them together all at once. This allows you to review code in consistent, and self-contained sessions, instead of as individual comments.

The most comprehensive import feature set

GitLab can import projects and issues from more sources (GitHub, Bitbucket, Google Code, FogBugz, Gitea and from any git URL) than GitHub or any other VCS. We even have you covered for your move from SVN to Git with comprehensive guides and documentation.

Export projects

GitLab allows you to export your project to other systems.

Create new branches from issues

In GitLab, you can quickly create a new branch from an issue on the issue tracker. It will include the issue number and title automatically, making it easy to track which branch belongs to which issue.

Allow edits from upstream maintainers in a fork

When a user opens a merge request from a fork, they are given the option to allow upstream maintainers to collaborate with them on the source branch. This allows the maintainers of the upstream project to make small fixes or rebase branches before merging, reducing the back and forth of accepting community contributions.

Create merge request from email

Create a merge request from email by sending in the merge request title, description, and source branch name. Alternatively use patch files to create a merge request without first pushing a branch.

First time contributor badge

Highlight first-time contributors in a project.

Ease of migration from other providers

GitLab lets you easily migrate all repos, issues and merge request data from your previous provider.

Advanced Global Search

Leverage Elasticsearch for faster, more advanced code search across your entire GitLab instance.

Advanced Syntax Search

Use advanced queries for more targeted search results.

Global Search API

Search globally through the API

Push rules

Reject new code and commits that don’t comply with company policy.

Block secret file push

Block important or secret files from being accidentally pushed to a live repository with push rules.

Remote repository push mirroring

Mirror a repository from your local server to elsewhere. Push mirroring is supported via HTTP and SSH using password authentication, and using public-key authentication with SSH.

Remote repository pull mirroring

Mirror a repository from a remote Git server to your local server, making it easy to keep local forks and replicas up to date.

Display merge request status for builds on Jenkins CI

Integrate with Jenkins CI and display the merge request build status directly from the merge request.

Import from GitLab.com

Import projects from GitLab.com to a private GitLab instance.

Restrict SSH Keys

Control the technology and key length of SSH keys used to access GitLab

Reject unsigned commits

GitLab Enterprise Edition Premium allows you to enforce GPG signatures by rejecting unsigned commits.

Verified Committer

Verify that a push only contains commits by the same user performing the push.

Git is fast

Git is really fast. Performing a diff, viewing history, committing and merging changes, obtaining any revision and any form of branching is very quick.

Git has smaller size requirements

A single repository in Git is typically a number of times smaller than the same repository in SVN.

Merge when pipeline succeeds

When reviewing a merge request that looks ready to merge but still has one or more CI/CD jobs running, you can set it to be merged automatically when the jobs pipeline succeeds.

Based on Git, a distributed VCS

Git, on which GitLab is built, is fully distributed. Every user has a complete copy of the repository, allowing for much faster access to history, easier branching and an overall better experience.

Snippets

Store and share code snippets to engage in a conversation about that piece of code. You can embed snippets on any blog or website using a single line of code.

Xcode integration

Open Xcode projects in Xcode directly from GitLab. Starting in Xcode 10, you can also sign in to GitLab in Xcode and access projects directly from the Xcode interface.

GPG Signed Commits

Sign commits and prove that a commit was performed by a certain user.

Publish your website from a private project for free

With GitLab Pages, you can create a private repository to hold your site content, and keep only the page source (HTML) available online.

Custom domains for GitLab Pages

With GitLab Pages websites, you can use a custom domain or subdomain.

Multiple custom domains for GitLab Pages

GitLab Pages allows you to add as many custom domains (known as domain aliases) pointing to a single website. A domain alias is like having multiple front doors to one location.

Secure custom domains (HTTPS) with GitLab Pages

Install a SSL/TLS certificate, at no cost, on a website set up with a custom domain served by GitLab Pages.

GitLab Pages custom domains verification

When adding a new custom domain, users must add an associated TXT record in order to verify they are the owner of the domain. That mechanism is used to prevent users from claiming domains they do not own.

GitLab Pages support all Static Site Generators

With GitLab, you can build any SSG, and also choose specific SSGs’ versions you want your site to build with (e.g. Middleman 4.1.1).

GitLab Pages example projects

Choose an example project to fork and get started with GitLab Pages.

GitLab Pages supports all Jekyll plugins

Besides building any Jekyll version you want, with GitLab Pages you can use all Jekyll plugins available.

Custom Error Pages (404) for GitLab Pages

GitLab Pages allows you to create custom error pages.

Access control for GitLab Pages

GitLab Pages allows you to set up custom access control for your site.

Globally distributed cloning with GitLab Geo

When development teams are spread across two or more geographical locations, but their GitLab instance is in a single location, fetching and cloning large repositories can take a long time. Built for distributed teams, GitLab Geo allows for read-only mirrors of your GitLab instance, reducing the time it takes to clone and fetch large repos and improving your collaboration process.

Ability to edit all fields of a merge request

GitLab Merge Requests are editable by the author, the project’s owners and users with master access. Every field is editable, as well as the target branch.

Configurable issue closing pattern

Define your own specific keywords to close one or more issues as soon as a merge request is merged.

Work in Progress merge requests (WIP)

Prevent merge requests from accidentally being accepted before they’re completely ready by marking them as Work In Progress (WIP). This gives you all the code review power of merge requests, while protecting unfinished work.

Custom Git Hooks

Leverage the power of Git Hooks and chain them together to fire off custom scripts when certain actions occur on the repository. If the commit is declined or an error occurs during the Git hook check, the error message of the hook will be present in GitLab’s UI. GitLab supports all types of hooks.

Git LFS 2.0 support

Manage large files such as audio, video and graphics files with the help of Git LFS. Git LFS 2.0 file locking support helps large teams work with binary assets and is integrated with our native file locking feature.

Contribution Analytics

View contributions per member of a group

Keep personal email private

Use a noreply email address for your commits instead of your personal email address private.

Project badges

First-class support for badges that are commonly added to a Project’s README, so that they are shown with the project description.

Instance file templates

Define custom LICENSE, .gitignore, Dockerfile and .gitlab-ci.yml templates for your GitLab instance to make consistency easier.

Group file templates

Define custom LICENSE, .gitignore, Dockerfile and .gitlab-ci.yml templates for a Group to make consistency easier.

Code Owners

Assign Code Owners to files to indicate the team members responsible for code in your project using a CODEOWNERS file. Code owners are assigned automatically as merge request approvers, can be set as required and shown when viewing files.

Git protocol v2 support

Git’s wire protocol defines how clones, fetches and pushes are communicated between the client and server. Git protocol v2 improves performance of fetch commands and enables future protocol improvements.

Deduplicate Git objects for forked repositories

Reduce disk storage requirements for fork networks by pooling Git objects.

The best place for large open source projects

GitLab is meant to be the best place for any software project. The team behind GitLab is addressing issues that maintainers and contributors to large open source projects are facing, to make it easier to do both.

Track Description Changes

View the full history of description updates in issues, merge requests, and epics.

Track Comment Changes

View the full history of comment updates.

Drag and Drop Tasks

Drag and drop tasks in a task lists.

Rich Object Summary on Link Hover

View an information-rich summary by hovering over links to users, issues, merge requests, and other objects in GitLab.

Create GitLab Branch from Jira Development Panel

Create a GitLab branch from within the development panel of a JIRA issue.

Create GitLab Merge Request from Jira Development Panel

Create a GitLab merge request from within the development panel of a JIRA issue.

Navigate to method/function in a merge request diff

When viewing a merge request diff, navigate directly to a method/function in a changed file.

Supports geolocation-aware DNS

Having Geo replicated server(s) can make local pulls go more quickly, but without support for Geolocation-aware DNS, developers need to reconfigure their tools manually to point to their nearest geo replicated server. Users using Geolocation-aware DNS can be transparently directed to the closest server available and can access repository data faster.

Advanced global search installed as default search

Advanced global search via ElasticSearch is installed and enabled as part of the core installation and provides the default search capability

Mercurial repository hosting

Hosts Mercurial DVCS repositories.

IP Whitelisting

IP Whitelisting defines safe IP network addresses from which clients can access and interact with the repository server. This helps prevent unwanted third parties from accessing your account even if they have acquired a team member’s email address and password.

Contributor agreements

Users can be required to sign one or more contributor agreements before being able to submit a change in a project.

Assignee

Assign a user to an issue or a merge request, indicating responsibility for it.

Merge approvals

When a project requires multiple sign-offs, GitLab Enterprise Edition enables you to make sure every merge request is approved by one or more people. Merge request approvals allow you to set the number of necessary approvals and predefine a list of approvers that will need to approve every merge request in a project, and in-turn improve your code’s quality.

Image Discussions

Within a commit view or a merge request diff view, and with respect to a specific location of an image, you can have a resolvable discussion. Have multiple discussions specifying different areas of an image.

Merge Request Commit Discussions

Comment on a commit within the context of a merge request itself

Multiple approvals in code review

In GitLab, to ensure strict code review, you can require a specific number of approvals on a merge request by different users before being able to merge it. You can undo an approval by removing it after the fact.

Approval rules for code review

Make sure the right people review merge requests with approval rules by specifying lists of eligible approvers and minimum number of approvals for each. This makes it easy to request review from different teams like Engineering, UX and Product.

Inline commenting and discussion resolution

Code or text review is faster and more effective with inline comments in merge requests. Leave comments and resolve discussions on specific lines of code. In GitLab, Merge Request inline comments are interpreted as a discussion and can be left on any line, changed or unchanged. You can configure your project to only accept merge requests when all discussions are resolved.

Code Owners

Assign Code Owners to files to indicate the team members responsible for code in your project using a CODEOWNERS file. Code owners are assigned automatically as merge request approvers, can be set as required and shown when viewing files.

Suggest changes

Collaborating on merge requests without copy/pasting to accept a suggested change. Changes can be suggested when leaving a comment on a merge request diff and accepted with a single click.

Code review dashboards

Dashboards with a filterable set of code reviews (could be by project, by user, by branch, by status, or a combination of those). Dashboards includes code review status and links to get to them. This makes it easy to see what is going on with code reviews for a desired subset.

Contributor agreements

Users can be required to sign one or more contributor agreements before being able to submit a change in a project.

Robot comments

Support for inline comments that are generated by automated third-party systems, for example robot comments can be used to represent the results of code analyzers.

Works with multiple repository types

Supports more than one repository type, such as Git, Subversion, Perforce, CVS, Mercurial.

Allow/deny merge based on votes

Allow or deny a merge based on vote tally from reviewers. Provides more flexibility in determining whether to merge changes or not.

Web IDE

Contribute to projects faster by using the Web IDE to avoid context switching in your local development environment. The Web IDE is integrated with merge requests and GitLab CI so that you can resolve feedback, fix failing tests and preview changes live with client side evaluation without leaving the Web IDE.

Web Terminal for Web IDE

Interact with your code in a Web Terminal in the Web IDE to inspect API responses, experiment in a REPL, or compile your code.

Built-in CI/CD

GitLab has built-in Continuous Integration/Continuous Delivery, for free, no need to install it separately. Use it to build, test, and deploy your website (GitLab Pages) or webapp. The job results are displayed on merge requests for easy access.

Built-in and custom project templates

When creating a new project, you can choose to kickstart your project from a predefined template that already has some working example code and CI preconfigured. In addition, you can define a custom project templates by assigning a group. Child projects of this group are available as templates when creating a new project.

Browser Performance Testing

Easily detect performance regressions for web apps, prior to merging into master. Browser Performance Testing is included in Auto DevOps, providing automatic performance analytics of the root page with zero configuration.

CI/CD for external repo

Connect your projects hosted on external services (like GitHub or Bitbucket) and leverage the power of GitLab CI/CD pipelines to build, test, and deploy your applications easily.

CI/CD for GitHub

Connect your projects hosted on GitHub and leverage the power of GitLab CI/CD pipelines to build, test, and deploy your applications easily.

See JUnit test summaries in merge request widget

GitLab allows you to view JUnit test results from the merge request widget, giving you insight into quality impacts of your changes.

Free CI/CD with shared or personal Runners

GitLab.com has shared Runners that allow you to use GitLab CI/CD completely free up to 2000 build minutes for private projects and unlimited for public projects. Alternatively, you can set up your own Runner for faster build processing, unlimited build minutes, or special requirements.

CI/CD Horizontal Autoscaling

GitLab CI/CD cloud native architecture can easily scale horizontally by adding new nodes if the workload increases. GitLab Runners can automatically spin up and down new containers to ensure pipelines are processed immediately and minimize costs.

Online visualization of HTML artifacts

Access your test reports, code quality and coverage information directly from your browser, with no need to download them locally.

Scheduled triggering of pipelines

You can make your pipelines run on a schedule in a cron-like environment.

Code Quality

Code Quality reports, available in the merge request widget area, give you an early insight into how the change will affect the health of your code before deciding if you want to accept it.

Protected variables

You can mark a variable as “protected” to make it available only to jobs running on protected branches, therefore only authorized users can get access to it.

Group-level variables

Define variables at the group level and use them in any project in the group.

Customizable path for CI/CD configuration

You can define a custom path into your repository for your CI/CD configuration file.

Run CI/CD jobs on Windows

GitLab Runner supports Windows and can run jobs natively on this platform. You can automatically build, test, and deploy Windows-based projects by leveraging PowerShell or batch files.

Run CI/CD jobs on macOS

GitLab Runner supports macOS and can run jobs natively on this platform. You can automatically build, test, and deploy for macOS based projects by leveraging shell scripts and command line tools.

Run CI/CD jobs on Linux ARM

GitLab Runner supports Linux operating systems on ARM architectures and can run jobs natively on this platform. You can automatically build, test, and deploy for Linux ARM based projects by leveraging shell scripts and command line tools.

Run CI/CD jobs on FreeBSD

GitLab Runner supports FreeBSD and can run jobs natively on this platform. You can automatically build, test, and deploy for FreeBSD-based projects by leveraging shell scripts and command line tools.

Show code coverage rate for your pipelines

GitLab is able to parse job output logs and search, via a customizable regex, any information created by tools like SimpleCov to get code coverage. Data is automatically available in the UI and also as a badge you can embedd in any HTML page or publish using GitLab Pages.

Protected Runners

Protected Runners allow you to protect your sensitive information, for example deployment credentials, by allowing only jobs running on protected branches to access them.

Minimal CI/CD configuration

GitLab CI/CD requires less configuration for your pipelines than other similar setups like Jenkins.

Automatic Retry for Failed CI Jobs

You can specify a retry keyword in your .gitlab-ci.yml file to make GitLab CI/CD retry a job for a specific number of times before marking it as failed.

Pipelines security

The ability of running CI/CD pipelines on protected branches is checked against a set of security rules that defines if you’re allowed or not. It includes creating new pipelines, retrying jobs, and perform manual actions.

Include external files in CI/CD pipeline definition

You can include external files in your pipeline definition file, using them as templates to reuse snippets for common jobs.

Instance file templates

Define custom LICENSE, .gitignore, Dockerfile and .gitlab-ci.yml templates for your GitLab instance to make consistency easier.

Group file templates

Define custom LICENSE, .gitignore, Dockerfile and .gitlab-ci.yml templates for a Group to make consistency easier.

Run jobs only when there are changes to a file or path

Jobs can be configured to run only when there are changes to a specific file or path, giving you control over execution to allow for more complex build pipelines optimized for the changes in each commit.

Run jobs only/except in the context of a merge request

Using the merge_requests value with only/except keywords allows you to configure jobs to run only (or except) when in the context of a merge request. This allows finer control over pipeline behavior, and also allows access to new environment variables indicating the target branch and merge request ID when relevant, offering opportunities for implementation of other more advanced behaviors.

Pipeline deletion

Deleting a pipeline is possible using the API, which allows for cases where perhaps secrets have been leaked in a pipeline, many unneeded pipelines have been created, or other issues have occurred where pipelines need to be deleted.

Explicit support for monorepos

The ability to execute jobs only/except when there are changes for a given path or file support monorepos where many microservices are contained in a single repo.

Server support for Windows and Mac

Support for running the server on Windows and Mac operating systems

Details on duration for each command execution in GitLab CI/CD

Other CI systems show execution time for each single command run in CI jobs, not just the overall time. We’re reconsidering how job output logs are managed in order to add this feature as well.

Step folding for CI/CD logs

Collapse the job log output for each command.

Bad test quarantine

Don’t let red builds become the norm. Across all tests, keep flakey or broken tests out of sight (but not out of mind), and keep the build green with one-click quarantine of tests.

Define multiple pipelines per repo

While GitLab has multi-project piplines that give you a view accross projects, each pipleine definition live in a YAML file tied to a specific project. Today, GitLab lacks the ability to define multiple pipelines in a single YAML file.

Global Docker registry browser

A sinle UI view into images accross multiple repositories.

Global Kubernetes cluster configuration

A sinle UI view into Kubernetes cluster configuration accross multiple repositories.

First class container building

The ability to specify that a container should be built during a CI/CD job without needing to specify the implementation details.

Built-in Container Registry

GitLab Container Registry is a secure and private registry for Docker images. It allows for easy upload and download of images from GitLab CI. It is fully integrated with Git repository management.

Built for using containers and Docker

GitLab ships with its own Container Registry, Docker CI Runner, and is ready for a complete CI/CD container workflow. There is no need to install, configure, or maintain additional plugins.

Docker image support

Supports storage and retreival of Docker style containers.

Container registry webhooks

Trigger actions after a successful push to a registry to integrate Docker Hub with other services.

Container registry high availability

Highly available through the use of multiple replicas of all containers and metadata such that if a machine fails, the regitry continues to operate and can be repaired.

Container registry geographic replication

Supports distributed teams by running multiple registry instances across several regions and syncing between data centers.

Supports private container registries

Offers the ability to have private container registries and repositories

SaaS container registry offering

The container registry ia available as a software service.

Self-managed container registry offering

Container registry which is available to be self-installed and self-managed in an organizations data center, co-hosted, or in a chosen cloud provider.

Cloud Native

GitLab and its CI/CD is Cloud Native, purpose built for the cloud model. GitLab can be easily deployed on Kubernetes and used to deploy your application to Kubernetes with support support out of the box.

Container debugging with an integrated web terminal

Easily debug your containers in any of your environments using the built-in GitLab Web Terminal. GitLab can open a terminal session directly from your environment if your application is deployed on Kubernetes. This is a very powerful feature where you can quickly debug issues without leaving the comfort of your web browser.

Use container registry through REST API

Enables support for automation and integration of container registry through a REST API.

Helm chart repository support

Supports storage and retreival of Helm charts.

Global Docker registry browser

A sinle UI view into images accross multiple repositories.

Full Binary Repository

A binary repository is a software repository for packages, artifacts and their corresponding metadata. It can be used to store binary files produced by an organization itself, such as product releases and nightly product builds, or for third party binaries which must be treated differently for both technical and legal reasons.

Full Binary Repository

A binary repository is a software repository for packages, artifacts and their corresponding metadata. It can be used to store binary files produced by an organization itself, such as product releases and nightly product builds, or for third party binaries which must be treated differently for both technical and legal reasons.

Security Dashboards

Security Dashboard report the latest security status of the default branch for each project

Static Application Security Testing