[New Partner Request] glab CLI for GitLab

Thank you for your interest as a partner with GitLab - we are glad you're here.

The initial step in exploring a potential partnership with GitLab is twofold: determine how GitLab will interface with your product and define the business relationship between GitLab and your company. GitLab is intentional about documenting in a manner that creates a single source of truth. We value asynchronous communication and transparency with our partners.

The Alliances team manages new partner requests and will review the issue. Generally, you will receive a response from GitLab within two weeks of submitting a new partner issue. This will either be an update on the status or a request for additional information.

Partnership Overview

Please include details about your company, the technical integration envisioned, end-user benefits and business relationship that you would ideally want. Our team will review and follow up with next steps.

📌 Don't forget to title this issue [New Partner Request] 'Company Name'

Tell us more about your company. What do you do, how many employees, when were you founded, etc?

I am applying as an individual contributor to GitLab. I created glab when my current company moved their codebase from GitHub to GitLab. GitHub has a CLI tool gh that helps to work easily with GitHub Issues and PRs without having to visit the github.com.

Switching to GitLab, we wanted a similar experience which compelled me to write glab with similar features as gh and support for all platforms without dependencies aside git. However, some of its features can be used if git is not installed.

glab, as an open-source work, has now been adopted by many developers and many are still contributing to its development and maintenance

What does the integration do? How do the two products work together for our joint customers?

GLab is an open-source GitLab CLI tool written in Go (golang) to help work seamlessly with GitLab from the command line. It allows developers to work with issues, merge requests, watch running pipelines directly from the CLI, CI liniting among other features.

Below snippets show commands provided by glab and a usage example:

$ glab
GLab is an open source Gitlab Cli tool bringing GitLab to your command line

Usage:
  glab <command> <subcommand> [flags]
  glab [command]

Examples:
  $ glab issue create
  $ glab mr list --merged
  $ glab pipeline list


Available Commands:
  check-update Check for latest glab releases
  config       Configuration
  help         Help about any command
  issue        Create, view and manage remote issues
  label        Manage labels on remote
  mr           Create, view and manage merge requests
  pipeline     Manage pipelines
  repo         Work with GitLab repositories and projects
  version      show glab version information

Flags:
  -h, --help      help for glab
  -v, --version   show glab version information

Use "glab [command] --help" for more information about a command.

Viewing list of Issues

$ glab issue list

Showing issues 2 of 2 on glab-cli/test

#2      This is a test issue title      (bug, frontend)         about 5 days ago
#1      This is a test issue            (label1, label2)        about 6 days ago

Is the integration/workflow with GitLab already completed?

Yes, but I plan to include more features in later releases
No

Do you use GitLab for your own internal development? (Optional) It's helpful to learn more about your developer toolstack and what the ecosystem is using so that we can support our partners and customers better.

GitLab Stages - Integration fit

What GitLab product stage does your company align with most? (https://about.gitlab.com/direction/maturity/)

Secure and Defend Product Category fit

If you are a Secure or Defend partner, which product category do you align with most? For more information, please visit the Secure Partner Integration - Onboarding Process page.

Requirements to be an Ecosystem Partner

Which of the following steps have you completed?

Note: New ecosystem partners filling out this issue, it is not a requirement to have all of these completed before submitting your first issue. This will be used when we are ready for Step 2 discussions.

- Completed integration and I am ready to show a demo
- Documented publicly available information on the integration (https://clementsam.tech/glab)
- Identified mutual customer(s)
- Submitted a merge request to be listed on the GitLab Partners Page. Follow these instructions on how to get your app listed.

Additional Requests

I would like to request a GitLab EE Ultimate license to develop and test our integration
I would like to request a dedicated project under the Alliance Group and/or GitLab.com sandbox project
I have a marketing request or go-to-market idea
I have a Public Relations (PR)/ External Communications Request
Other - please provide additional information

Once you have completed this issue, make sure to assign the issue or mention @abrandenburg in the comments

What if I am having an issue with building my integration? We're always here to help you through your efforts of integration. If there's a missing API call from our current API, or you ran into other difficulties in your development please feel free to create a new issue on the Community Edition issue tracker and apply the Ecosystem label.

Do Not Edit Below

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information