glab-repo

glab repo

Work with GitLab repositories and projects.

Quick start

# Clone a repository
glab repo clone group/project

# Clone the project's wiki repository
glab repo clone --wiki group/project

# Create new repository
glab repo create my-new-project --public

# Fork a repository
glab repo fork upstream/project

# View repository details
glab repo view

# Add a Git remote from a GitLab project reference
glab repo remote add group/project --name upstream

# Prune local branches whose MRs have been merged
glab repo prune --dry-run
glab repo prune --yes

# Search for repositories
glab repo search "keyword"

Common workflows

Starting new project

1. Create repository:

   glab repo create my-project \
     --public \
     --description "My awesome project"
   
   # Create with README
   glab repo create my-project \
     --public \
     --readme
   

   Note: glab repo create --readme clones the newly created repository instead of using git init, ensuring a clean local copy with the initial README.

   A path containing nested groups preserves the complete namespace. For example, glab repo create group/subgroup/my-project creates my-project under group/subgroup, not only the final subgroup.

2. Clone locally (if not using --readme):

   glab repo clone my-username/my-project
   cd my-project
   

   To clone only the GitLab wiki, pass --wiki with one project reference. It cannot be combined with group-wide --group cloning, and it fails clearly when the project's wiki is disabled.

   glab repo clone --wiki group/project
   

   SSH configurations that map gitlab.com to the official altssh.gitlab.com endpoint are recognized as GitLab.com rather than as a separate self-managed host.

   For self-managed hosts that include a port, glab keys subfolder config lookup on the full host with port. If a repository resolves to the wrong API host or misses a configured subfolder, verify the exact host key in the config file at glab config path includes the port.