gitlab-ci-usage

Validate GitLab CI YAML syntax and keyword usage in .gitlab-ci.yml.

Updated Nov 12, 2017

Search Tags:#workflow #troubleshooting #yaml #gitlab #lint #ci #include

One-click install

npx skills add https://github.com/ak110/dotfiles --skill gitlab-ci-usage

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gitlab-ci-usage
Source: https://github.com/ak110/dotfiles/tree/main/plugins/agent-toolkit/skills/gitlab-ci-usage
Command: npx skills add https://github.com/ak110/dotfiles --skill gitlab-ci-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This reference consolidates key GitLab CI YAML keywords, common patterns, lint methods, and troubleshooting guidance to speed up editing of .gitlab-ci.yml.

Core Features & Use Cases

Centralized reference for keyword semantics, include handling, and artifact definitions.
Practical patterns for rules, needs, extends, and includes to produce reliable pipelines.
Use Case: When starting a new pipeline, consult this guide to choose correct job startup conditions and dependencies.

Quick Start

Consult official GitLab CI YAML docs and run lint checks against your .gitlab-ci.yml to ensure correct syntax and behavior.

Frequently Asked Questions about gitlab-ci-usage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate and lint a .gitlab-ci.yml file for syntax errors?▼

To lint a .gitlab-ci.yml file, consult official GitLab YAML docs and use the GitLab lint API or local validators to verify syntax, keyword semantics, and pipeline behavior before pushing changes.

What is the correct way to use includes and rules in GitLab CI YAML?▼

GitLab CI YAML uses includes to combine external configurations and rules to define job startup conditions. Consult a centralized keyword reference to apply reliable patterns for conditional logic and dependencies.

Why does my GitLab CI pipeline job run when I expect it to be skipped?▼

GitLab CI pipeline behavior depends on rules and conditional logic in your YAML. Troubleshoot by reviewing keyword usage in the reference, checking needs and extends definitions, and running lint checks to validate semantics.

Can I use local validators to check GitLab CI YAML without pushing to a project?▼

Yes, you can use local validators or the GitLab lint API to check .gitlab-ci.yml syntax and semantics locally. This allows you to resolve keyword usage, artifact definitions, and pipeline rules across project contexts before committing.

What are the most common patterns for defining artifacts and needs in GitLab CI?▼

Common GitLab CI patterns involve using needs to define job dependencies and artifacts to pass build outputs between jobs. Refer to a keyword semantics guide to ensure correct artifact definitions and reliable pipeline execution.