Gitlab hero border pattern left svg Gitlab hero border pattern right svg

GitLab CI/CD for GitHub FAQ

Release date


GitLab Press Spokespeople

Mark Pundsack

Q: What is covered in today’s announcement?

A: With GitLab CI/CD for GitHub, enterprises working with multiple different types of code repositories can now standardize on GitLab CI/CD for seamless consistency across both their GitHub and GitLab code repositories. Open source projects that host their code on GitHub can take advantage of CI/CD on, where GitLab offers top tier features for free to open source projects.

Q: What is the headline of the press release?

A: GitLab Brings Industry-Leading Continuous Integration and Deployment to GitHub Community

Q: Who is quoted in the press release?

A: Sid Sijbrandij: “Continuous integration and deployment form the backbone of modern DevOps,” said Sid Sijbrandij, CEO and co-founder of GitLab. "With this new offering, businesses and open source projects that use GitHub as a code repository will have access to GitLab’s industry leading CI/CD capabilities."

Q: Where can I view a copy of the press release?


Q: Is there a blog post providing more detail on the announcement?

A: Yes, there are more details in the 10.6 release post [link to blog post]

Q: Is there a landing page for the feature?

A: Yes, [will go live 2018-03-22] will also redirect to the longer URL and can be used in social, emails, etc.

Q: Are there other activities associated with this announcement?

A: We are running a promotion that makes this feature available (normally a Silver feature) part of the Free tier on for one year. (Self-hosted customers have access in the Premium tier.)

Q: Is GitLab CI/CD for GitHub generally available?

A: Yes

Q: Does GitLab CI/CD also integrate with Bitbucket? Other solutions?

A: Yes, but the process is more manual. GitLab CI/CD can connect to any git repo via URL, including Bitbucket, and configure status webhooks manually. Docs on how to manually enable GitLab CI/CD. (With GitHub the process is all automatic.)

Q: How does GitLab CI/CD integration to GitHub work?

A: GitLab users can create a CI/CD project in GitLab connected to an external GitHub code repository, which automatically prompts GitLab CI/CD to run whenever code is pushed to GitHub and post CI/CD results back to GitHub when completed.

Q: What are the key features of GitLab CI/CD for GitHub?

A: The ability to easily set up GitLab CI/CD on GitHub is the main feature enabling continuous integration, security testing, container registry, CD/release automation, configuration management, and monitoring.

Q: What opportunity is GitLab addressing with GitLab CI/CD for GitHub?

A: Several  

Enterprise opportunity

With large enterprises we have 2 opportunities:

  1. New starting point for GitLab adoption. Many enterprises adopt GitLab gradually over time starting with SCM. The GitHub Integration provides another starting point for enterprises to begin adopting GitLab by using CI/CD first.
  2. Standardize on GitLab CI/CD with disparate SCM solutions. How many GitLab users do they need if they are using GitHub for SCM?

Open Source Projects opportunity

GitLab is committed to supporting open source. ON, open source projects get unlimited concurrent jobs and 50K CI pipeline minutes per month for free. The GitHub Integration allows projects who host their code on GitHub to use GitLab for CI/CD for free.

Broader GitHub community opportunity

By making GitLab CI/CD for GitHub available free of charge as part of our Free tier we are allowing anyone who uses to host their code, to use for their CI/CD. This is a way to expand the reach of GitLab and expose GitLab to users who may otherwise have not tried GitLab out.

Gemnasium Customer opportunity

Gemnasium customers who are using GitHub now have a migration path to use the Gemnasium features we’ve built (and will build) into GitLab CI/CD Security Testing. Note: Gemnasium customers will need Ultimate/Gold to take advantage of Security Testing.

Q: Is GitLab CI/CD for GitHub available as a standalone product?

A: No, GitLab CI/CD is a Premium functionality and is not a standalone product.

Q: How is GitLab CI/CD for GitHub priced?

A: GitLab CI/CD for GitHub is a feature of GitLab without stand-alone pricing.

It is part of our Premium (Self-hosted) & Silver ( Tiers - $19 /user /month (For all GitLab Premium features including CI/CD for GitHub.)

Promotionally, we will make the GitLab CI/CD feature available as part of the Free Tier on through 2019-09-22.

Q: How many GitLab users are needed?

A customer only needs 1 service account on GitLab to run pipelines for GitHub code, but will benefit from having more user accounts.

What are the pro/cons for the business if they create one service account and use it to run their pipelines?



Do they need users for each developer using GitHub/Bitbucket - why/why not?

No - It’s not necessary, but enabling developers grants benefits:

Do they need users for QA/ops engineers building the pipelines?

Yes - this should be sold against Jenkins / Travis, think about how many users you'd need to access those tools, and that is the user count that should have access to GitLab.

Q: What are the details of the launch promotion?

A: GitLab CI/CD for external repos, including GitLab CI/CD for GitHub will be available as part of the Free tier of for one-year plus extended six-month (through 2019-09-22). After 2019-09-22 we plan to move the feature to be part of Silver. Note: this is for only - self-hosted customers will only have access in Premium & Ultimate.

Q: Are there any other features offered as part of a different tier promotionally?

A: At this time, no. This is the first time we’ve offered a feature like this promotionally in a different tier than it will eventually end up in,.

Q: Is GitLab CI/CD for GitHub available in both hosted and self-hosted versions?

A: Yes, GitLab CI/CD for GitHub is available on all hosted versions and is available self-hosted on GitLab Premium and Ultimate.

Q: What product plans include GitLab CI/CD for GitHub?

A: Self-hosted: Premium and Ultimate Free, Bronze, Silver, and Gold (through 2019-09-22) Silver, Gold (after 2019-09-22)

Q: What stages of DevOps Lifecycle work with GitHub?

Stage Product Category Works with GitHub? Notes
Plan Portfolio management No  
Plan Issue Tracking No  
Create Version Control No Repos are Mirrored, which is needed for CI/CD, but there’s no mechanism for Merge Conflicts so you can’t actively use the GitLab Repo
Create Code Review No  
Verify Continuous integration Yes  
Verify Security Testing Yes  
Package Container Registry Yes On by default once instance container registry enabled
Release CD/Release automation Yes E.g. You CAN deploy to GCP using the GKE Integration
Configure Configuration management Yes  
Monitor Monitoring Yes  

Q: Do we have current customers using GitLab CI/CD for GitHub?

A: No, GitLab CI/CD for GitHub is being released and launched on the same day. As such, it will not be available for customers to use until after GitLab 10.6  is released on 2018-03-22.

Q: Will GitLab CI/CD for GitHub be available on the GitHub marketplace?

A: We have not made a determination if it will or will not be in the marketplace. It is a

possibility, but requires additional complexity such as augmenting how we price. It is not available today as part of the marketplace.

Q: What press did we get?