GitLab CLI (glab) 命令大全：合并请求、CI/CD、项目管理完整指南

gitlab-cli-skills by vince-winkintel/gitlab-cli-skills

367 周安装量

11 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/vince-winkintel/gitlab-cli-skills --skill gitlab-cli-skills

开发自动化开发运维

🇨🇳中文介绍

GitLab CLI 技能

全面的 GitLab CLI (glab) 命令参考和工作流。

快速开始

# 首次设置
glab auth login

# 常用操作
glab mr create --fill              # 从当前分支创建 MR
glab issue create                  # 创建议题
glab ci view                       # 查看流水线状态
glab repo view --web              # 在浏览器中打开仓库

技能组织

此技能按 GitLab 领域路由到专门的子技能：

核心工作流：

glab-mr - 合并请求：创建、审查、批准、合并
glab-issue - 议题：创建、列出、更新、关闭、评论
glab-ci - CI/CD：流水线、作业、日志、制品
glab-repo - 仓库：克隆、创建、派生、管理

项目管理：

glab-milestone - 发布规划和里程碑跟踪

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

何时使用 glab 与 Web 界面

在以下情况使用 glab：

在脚本中自动化 GitLab 操作
在以终端为中心的工作流中工作
批量操作（多个 MR/议题）
与其他 CLI 工具集成
CI/CD 流水线工作流
无需浏览器上下文切换的快速导航

在以下情况使用 Web 界面：

带有行内评论的复杂差异审查
可视化合并冲突解决
配置仓库设置和权限
跨项目的高级搜索/筛选
审查安全扫描结果
管理群组/实例级设置

# 开始处理议题
glab issue view 123
git checkout -b 123-feature-name

# 准备好后创建 MR
glab mr create --fill --draft

# 标记为准备审查
glab mr update --ready

# 批准后合并
glab mr merge --when-pipeline-succeeds --remove-source-branch

# 列出您的审查队列
glab mr list --reviewer=@me --state=opened

# 审查一个 MR
glab mr checkout 456
glab mr diff
npm test

# 批准
glab mr approve 456
glab mr note 456 -m "LGTM! Nice work on the error handling."

# 检查流水线状态
glab ci status

# 查看失败的作业
glab ci view

# 获取作业日志
glab ci trace <job-id>

# 重试失败的作业
glab ci retry <job-id>

"我应该先创建 MR 还是先处理议题？"

需要跟踪工作吗？
├─ 是 → 先创建议题 (glab issue create)
│         然后：glab mr for <issue-id>
└─ 否 → 直接 MR (glab mr create --fill)

在以下情况使用 glab issue create + glab mr for：

工作需要在编码前进行讨论/批准
跟踪功能请求或错误
冲刺规划和分配
希望议题在 MR 合并时自动关闭

在以下情况直接使用 glab mr create：

快速修复或拼写错误
基于现有议题工作
热修复或紧急变更

"我应该使用哪个 CI 命令？"

您需要什么？
├─ 整体流水线状态 → glab ci status
├─ 可视化流水线视图 → glab ci view
├─ 特定作业日志 → glab ci trace <job-id>
├─ 下载构建制品 → glab ci artifact <ref> <job-name>
├─ 验证配置文件 → glab ci lint
├─ 触发新运行 → glab ci run
└─ 列出所有流水线 → glab ci list

流水线级别：glab ci status, glab ci view, glab ci run
作业级别：glab ci trace, glab job retry, glab job view
制品：glab ci artifact（按流水线）或通过 glab job 的作业制品

"克隆还是派生？"

您与仓库的关系是什么？
├─ 您有写入权限 → glab repo clone group/project
├─ 为他人项目做贡献：
│   ├─ 一次性贡献 → glab repo fork + 工作 + MR
│   └─ 持续贡献 → glab repo fork，然后定期同步
└─ 仅阅读/探索 → glab repo clone (或 view --web)

在以下情况派生：

您没有对原始仓库的写入权限
为开源项目做贡献
实验而不影响原始仓库
需要自己的副本进行长期工作

在以下情况克隆：

您是拥有写入权限的项目成员
处理组织/团队仓库
不需要个人副本

"项目标签与群组标签？"

标签应该放在哪里？
├─ 跨多个项目使用 → glab label create --group <group>
└─ 特定于一个项目 → glab label create (在项目目录中)

群组级标签：

跨组织的一致标签
示例：priority::high, type::bug, status::blocked
集中管理，由项目继承

项目级标签：

项目特定的工作流
示例：needs-ux-review, deploy-to-staging
由项目维护者管理

MR 和议题工作流：

从 glab-issue 开始以创建/跟踪工作
使用 glab-mr 创建关闭议题的 MR
脚本：scripts/create-mr-from-issue.sh 自动化此过程

使用 glab-ci 进行流水线级操作
使用 glab-job 进行单个作业操作
脚本：scripts/ci-debug.sh 用于快速故障诊断

使用 glab-repo 进行仓库管理
使用 glab-auth 进行认证设置
脚本：scripts/sync-fork.sh 用于派生同步

使用 glab-auth 进行初始认证
使用 glab-config 设置默认值和偏好
使用 glab-alias 获取自定义快捷方式

🇺🇸English

GitLab CLI Skills

Comprehensive GitLab CLI (glab) command reference and workflows.

Quick start

# First time setup
glab auth login

# Common operations
glab mr create --fill              # Create MR from current branch
glab issue create                  # Create issue
glab ci view                       # View pipeline status
glab repo view --web              # Open repo in browser

Skill organization

This skill routes to specialized sub-skills by GitLab domain:

Core Workflows:

glab-mr - Merge requests: create, review, approve, merge
glab-issue - Issues: create, list, update, close, comment
glab-ci - CI/CD: pipelines, jobs, logs, artifacts
glab-repo - Repositories: clone, create, fork, manage

Project Management:

glab-milestone - Release planning and milestone tracking
glab-iteration - Sprint/iteration management
glab-label - Label management and organization
glab-release - Software releases and versioning

Authentication & Config:

glab-auth - Login, logout, Docker registry auth
glab-config - CLI configuration and defaults
glab-ssh-key - SSH key management
glab-gpg-key - GPG keys for commit signing
glab-token - Personal and project access tokens

CI/CD Management:

glab-job - Individual job operations
glab-schedule - Scheduled pipelines and cron jobs
glab-variable - CI/CD variables and secrets
glab-securefile - Secure files for pipelines
glab-runner - Runner management: list, pause, delete (added v1.87.0)
glab-runner-controller - Runner controller and token management (EXPERIMENTAL, admin-only)

Collaboration:

glab-user - User profiles and information
glab-snippet - Code snippets (GitLab gists)
glab-incident - Incident management
glab-workitems - Work items: tasks, OKRs, key results, next-gen epics (added v1.87.0)

Advanced:

glab-api - Direct REST API calls
glab-cluster - Kubernetes cluster integration
glab-deploy-key - Deploy keys for automation
glab-quick-actions - GitLab slash command quick actions for batching state changes
glab-stack - Stacked/dependent merge requests
glab-opentofu - Terraform/OpenTofu state management

Utilities:

glab-alias - Custom command aliases
glab-completion - Shell autocompletion
glab-help - Command help and documentation
glab-version - Version information
glab-check-update - Update checker
glab-changelog - Changelog generation
glab-attestation - Software supply chain security
glab-duo - GitLab Duo AI assistant
glab-mcp - Model Context Protocol server for AI assistant integration (EXPERIMENTAL)

v1.89.0 Updates

v1.89.0+: 18 commands across 12 sub-skills now support --output json / -F json for structured output — raw GitLab API responses ideal for agent/automation parsing. Affected sub-skills: glab-release, glab-ci, glab-milestone, glab-schedule, glab-mr, glab-repo, glab-label, glab-deploy-key, glab-ssh-key, , , .

Other v1.89.0 changes:

glab-auth : glab auth login now prompts for SSH hostname separately from API hostname on self-hosted instances
glab-stack : glab stack sync --update-base flag added to rebase stack onto updated base branch
glab-release : --notes / --notes-file are now optional for glab release create and glab release update

When to use glab vs web UI

Use glab when:

Automating GitLab operations in scripts
Working in terminal-centric workflows
Batch operations (multiple MRs/issues)
Integration with other CLI tools
CI/CD pipeline workflows
Faster navigation without browser context switching

Use web UI when:

Complex diff review with inline comments
Visual merge conflict resolution
Configuring repo settings and permissions
Advanced search/filtering across projects
Reviewing security scanning results
Managing group/instance-level settings

Common workflows

Daily development

# Start work on issue
glab issue view 123
git checkout -b 123-feature-name

# Create MR when ready
glab mr create --fill --draft

# Mark ready for review
glab mr update --ready

# Merge after approval
glab mr merge --when-pipeline-succeeds --remove-source-branch

Code review

# List your review queue
glab mr list --reviewer=@me --state=opened

# Review an MR
glab mr checkout 456
glab mr diff
npm test

# Approve
glab mr approve 456
glab mr note 456 -m "LGTM! Nice work on the error handling."

CI/CD debugging

# Check pipeline status
glab ci status

# View failed jobs
glab ci view

# Get job logs
glab ci trace <job-id>

# Retry failed job
glab ci retry <job-id>

Decision Trees

"Should I create an MR or work on an issue first?"

Need to track work?
├─ Yes → Create issue first (glab issue create)
│         Then: glab mr for <issue-id>
└─ No → Direct MR (glab mr create --fill)

Useglab issue create + glab mr for when:

Work needs discussion/approval before coding
Tracking feature requests or bugs
Sprint planning and assignment
Want issue to auto-close when MR merges

Useglab mr create directly when:

Quick fixes or typos
Working from existing issue
Hotfixes or urgent changes

"Which CI command should I use?"

What do you need?
├─ Overall pipeline status → glab ci status
├─ Visual pipeline view → glab ci view
├─ Specific job logs → glab ci trace <job-id>
├─ Download build artifacts → glab ci artifact <ref> <job-name>
├─ Validate config file → glab ci lint
├─ Trigger new run → glab ci run
└─ List all pipelines → glab ci list

Quick reference:

Pipeline-level: glab ci status, glab ci view, glab ci run
Job-level: glab ci trace, glab job retry, glab job view
Artifacts: glab ci artifact (by pipeline) or job artifacts via glab job

"Clone or fork?"

What's your relationship to the repo?
├─ You have write access → glab repo clone group/project
├─ Contributing to someone else's project:
│   ├─ One-time contribution → glab repo fork + work + MR
│   └─ Ongoing contributions → glab repo fork, then sync regularly
└─ Just reading/exploring → glab repo clone (or view --web)

Fork when:

You don't have write access to the original repo
Contributing to open source projects
Experimenting without affecting the original
Need your own copy for long-term work

Clone when:

You're a project member with write access
Working on organization/team repositories
No need for a personal copy

"Project vs group labels?"

Where should the label live?
├─ Used across multiple projects → glab label create --group <group>
└─ Specific to one project → glab label create (in project directory)

Group-level labels:

Consistent labeling across organization
Examples: priority::high, type::bug, status::blocked
Managed centrally, inherited by projects

Project-level labels:

Project-specific workflows
Examples: needs-ux-review, deploy-to-staging
Managed by project maintainers

Related Skills

MR and Issue workflows:

Start with glab-issue to create/track work
Use glab-mr to create MR that closes issue
Script: scripts/create-mr-from-issue.sh automates this

CI/CD debugging:

Use glab-ci for pipeline-level operations
Use glab-job for individual job operations
Script: scripts/ci-debug.sh for quick failure diagnosis

Repository operations:

Use glab-repo for repository management
Use glab-auth for authentication setup
Script: scripts/sync-fork.sh for fork synchronization

Configuration:

Use glab-auth for initial authentication
Use glab-config to set defaults and preferences
Use glab-alias for custom shortcuts

Weekly Installs

367

Repository

vince-winkintel…i-skills

GitHub Stars

First Seen

Feb 6, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykWarn

Installed on

opencode362

github-copilot362

gemini-cli361

codex361

kimi-cli361

amp361

agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试

140,500 周安装