k3nny
3b0bcb72d3
Add --context KEY=VALUE[,...] (repeatable) to glint check. When two or more --context flags are given, glint evaluates every pipeline job across all contexts and prints a side-by-side comparison table: glint check --context branch=main --context branch=develop .yml Each column shows active / manual / skipped / blocked per job. Known context keys are branch, tag, source (case-insensitive); any other KEY=VALUE pair is treated as a CI variable override. The --changes / --changes-from changed-file list is shared across all contexts. Implicit branch=main / source=push defaults are skipped when --context is used. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
glint
Disclaimer: This tool was built through iterative AI-assisted development with Claude. It is experimental, incomplete, and not intended for production use. Coverage of GitLab CI keywords is best-effort and may lag behind GitLab's evolving spec. Use it at your own discretion — no correctness guarantees are made. Contributions and bug reports are welcome.
A local tool to validate and lint .gitlab-ci.yml pipelines without needing a GitLab server.
What it does
- Lints — 43 rules covering pipeline structure, keyword constraints,
needs:/dependencies:graphs, expression reachability, and deprecations (GL001–GL043); runglint explain <ID>for any rule - Resolves includes — local files, HTTPS URLs, GitLab project templates, and CI/CD Catalog components, with offline cache support
- Simulates context —
--branch,--tag,--sourceflags evaluaterules:if:andonly/exceptto show which jobs would be active, manual, or skipped;--context branch=main --context branch=developprints a multi-column comparison table across multiple contexts in one run - Multiple output formats —
--format text(default, ruff-style),json,sarif(GitHub Code Scanning / GitLab SAST),junit,github(PR annotations) - Project config —
.glint.ymlfor rule suppression, severity overrides, token/URL defaults;# glint: ignore RULEfor per-job inline suppression - Graph visualization —
glint graphprints a terminal job tree;glint graph pipelinerenders a GitLab CI-style SVG/PNG
See FEATURES.md for the complete feature reference and lint rules table, and ROADMAP.md for planned improvements.
Requirements
- Go 1.21 or later
- Task (optional, for development tasks)
Installation
git clone https://git.k3nny.fr/glint
cd glint
go build -o glint ./cmd/glint/...
Or with Task:
task build
Usage
glint [OPTIONS] <COMMAND>
Commands:
check Lint a pipeline file — exits 0 (clean) or 1 (errors found)
graph Visualise the pipeline as a job tree or Mermaid graph
explain Print description and fix for a lint rule
Run glint <command> --help for all flags. See USAGE.md for full
examples covering output formats, context simulation, remote includes, cache,
graph modes, and project configuration.
Development
This project uses Task as a task runner.
task # list available tasks
task build # compile the binary
task test # run Go unit tests
task lint-go # run go vet
task validate # run the binary against all testdata fixtures
task ci # full check: vet → test → build → validate
task build-windows # cross-compile for Windows x64 (requires a tagged commit → glint-<tag>.exe)
task build-linux # cross-compile for Linux x64 (requires a tagged commit → glint-<tag>-linux-amd64)
task clean # remove build artifacts
Project structure
.
├── cmd/glint/ # CLI entrypoint
├── internal/
│ ├── cicontext/ # CI variable context, rules:if: evaluator, job reachability
│ ├── fetcher/ # GitLab API client (project include fetching)
│ ├── graph/ # Mermaid and SVG/PNG graph generators
│ ├── linter/ # lint rules and findings
│ ├── model/ # pipeline data structures and YAML parser
│ └── resolver/ # extends: resolution and project include merging
├── testdata/ # sample pipelines used for manual validation
├── Taskfile.yml
└── go.mod