Adds project-level configuration and per-job suppression directives:
.glint.yml (searched from pipeline dir up to the git root):
- ignore: [GL007, GL032] — suppress rules globally for the project
- severity: {GL004: warning} — override rule severity (error/warning/ignore)
- stages: [quality] — extra stages beyond the pipeline's stages: block
- token: / url: / cache_dir: — defaults for flags; lower priority than
CLI flags and environment variables
Inline suppression (# glint: ignore):
- Place "# glint: ignore GL007" immediately before a job definition to
suppress that rule for the specific job only
- Multiple rules: "# glint: ignore GL007, GL032" (comma or space separated)
- Wildcard: "# glint: ignore all" suppresses every finding for the job
- Suppressions are scoped to the annotated job; pipeline-level findings
are unaffected
- Parsed from yaml.Node head/line comments in the first parse pass;
stored in Pipeline.Suppressions (root file only, not includes)
New packages: internal/config (Load, walk-up search, .git boundary stop)
New files: cmd/glint/filter.go (applyConfig, isSuppressed helpers)
Tests: config_test.go, parser_suppress_test.go, filter_test.go
Validate fixtures: testdata/config_ignored/, config_severity/, config_suppress/
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
13 KiB
Roadmap
This document tracks planned improvements to glint. Items are grouped by theme, roughly in priority order within each group. Nothing here is a commitment — the tool is experimental and the list will shift as real usage surfaces better priorities.
Context-aware validation — ✓ single-context shipped in v0.2.0; expression evaluator hardened post-v0.2.0; implicit defaults and --list-vars shipped v0.2.11; variable expansion and scalar handling shipped v0.2.13; workflow evaluation and output fixes shipped v0.2.14
Single-context simulation is fully implemented. Pass --branch, --tag, --source, or --var to either glint check or glint graph; jobs are evaluated and shown as active / manual / skipped.
# shipped: single-context simulation
glint check --branch develop .gitlab-ci.yml
glint check --tag v1.2.0 .gitlab-ci.yml
glint check --source merge_request_event --var CI_MERGE_REQUEST_TARGET_BRANCH_NAME=main .gitlab-ci.yml
glint graph tree --branch main .gitlab-ci.yml # tree annotated with [skipped] / [manual]
Shipped post-v0.2.0 (unreleased)
- ✓
workflow:rules:variables:propagation — variables defined on the matchingworkflow:rules:entry are injected into the evaluation context before jobrules:if:expressions are evaluated. Pipeline-levelvariables:defaults are also available. Priority chain (highest wins):--var> shortcuts > workflow-rule vars > pipeline defaults. - ✓ Expression evaluator: multi-line expressions — newlines in block-scalar and folded YAML
if:values are now treated as whitespace;||/&&on a continuation line evaluate correctly. - ✓ Expression evaluator:
${VAR}curly-brace syntax —${CI_COMMIT_BRANCH}is equivalent to$CI_COMMIT_BRANCHeverywhere. - ✓ Expression evaluator: regex flags —
/pattern/i,/pattern/m,/pattern/sare now supported;imaps to(?i)in Go's regexp. - ✓ Expression evaluator: variable as regex RHS —
$BRANCH =~ $PATTERNwhere$PATTERNholds a/regex/string is evaluated correctly. - ✓ Expression evaluator: bare
true/falsekeywords — treated as the strings"true"/"false"matching GitLab CI's own behaviour;$GATEWAY_ENABLED == truenow evaluates correctly. - ✓ Expression evaluator: integer literals —
$COUNT == 4,$ENABLED == 1,$DISABLED == 0compare as decimal strings.
Implicit default context — ✓ shipped v0.2.11; glint check and glint graph default to --branch main --source push when no context flag is given, so rules:if: expressions are always evaluated out of the box.
— ✓ shipped v0.2.11; prints sorted --list-vars debug flagKEY=VALUE of all collected variables (pipeline YAML + included files + workflow-rule union + effective context) to stderr.
Shipped in v0.2.13
- ✓ Variable expansion —
$VAR/${VAR}references within variable values are expanded after all sources are merged; transitive chains resolve over multiple passes; visible in--list-varseffective-context output. - ✓ Non-string scalar variables —
BUILD: true,RETRIES: 3and similar bare boolean/integer values now render correctly in--list-varsand are injected into the evaluation context as string equivalents; previously shown as(complex)and silently dropped. - ✓ YAML
\/escape in double-quoted strings — regex patterns like/^us\//in double-quotedif:blocks no longer cause a parse error; the raw bytes are preprocessed before YAML unmarshalling.
Shipped in v0.2.14
- ✓ Workflow rule strict evaluation — workflow
rules:if:now uses strict mode (parse failure → skip rule, not match); fixes premature matching that blocked later rules and injected wrong variables. - ✓ Single
=operator —=is now accepted as an alias for==inrules:if:expressions, matching common user intent. - ✓ Source location through
extends:resolution —FileandLineare now preserved when a job is rebuilt via extends, so findings reference the correct source location. - ✓ Sorted findings output — findings are sorted by
(File, Line, Rule); same-file issues group together in line order. - ✓ Consistent warning format — all warnings use ruff-style
path: [warning] messageformat. - ✓
--version/-vflag — prints compiled version; version also shown at the top of every--helpoutput.
Remaining work
- Multi-context simulation — run multiple contexts in one invocation and print a comparison table:
glint check --context branch=main --context branch=develop --context tag=v1.0.0 .gitlab-ci.yml - Context-scoped linting — skip
needs:/dependencies:cross-checks for jobs that are statically unreachable in the given context rules:changes:evaluation — path glob evaluation against the local git tree
Lint coverage
The current rule set covers the most common sources of broken pipelines. These are the gaps most likely to matter in practice.
Variable reference validation (GL032)— ✓ shipped v0.2.11; warns when arules:if:expression references$VAR/${VAR}not declared anywhere in pipeline YAML; predefined GitLab namespaces (CI_*,GITLAB_*, …) exempt; variables from included files are also considered— ✓ shipped v0.2.15; warns when every rule in a job'srules:if:static reachability (GL033)rules:block haswhen: never, making the job permanently excluded from any pipeline run; noif:evaluation required— ✓ shipped v0.2.16; map form requiresservices:validation (GL034)name;aliasmust be a valid DNS label— ✓ shipped v0.2.16; warns when a path starts withrules:changes/rules:existsabsolute path detection (GL035)/; GitLab CI paths are always relative to the repo root— ✓ shipped v0.2.16; validates job-level andtimeoutformat validation (GL036)default.timeoutagainst recognised GitLab CI duration strings— ✓ shipped v0.2.16;id_tokens:/secrets:required-key checks (GL037, GL038)id_tokensentries must haveaud;secretsentries must declare a provider— ✓ shipped v0.2.16; warns when the publish directory is missing frompages:publish+artifacts.pathsconsistency (GL039)artifacts.pathsDuplicate stage names (GL040)— ✓ shipped v0.2.16; warns when a stage appears more than once instages:— ✓ shipped v0.2.16; warns when entries look like glob patternscache:key:filesmust be exact paths (GL041)Unreachable jobs— covered by GL033 (shipped v0.2.15); every-when:neverrules block is statically deadinherit:completeness — flag when a job overrides a default field that would requireinherit: default: falseto suppress
Include resolution
— ✓ shipped in v0.2.0; local files are read from disk, recursively resolved, and merged before lintinginclude: local:full resolution— ✓ shipped post-v0.2.0; plain HTTPS URLs are fetched (unauthenticated), parsed, and merged; sub-includes are resolved recursively; unreachable URLs emitinclude: remote:(URL)[WARNING]and linting continuesRecursive include depth limit— ✓ shipped v0.2.17; depth capped at 100 (matching GitLab); project/component includes now tracked in visited set to prevent cross-file cyclesOffline mode / cache— ✓ shipped v0.2.17;--cache-dir DIRpersists fetched templates;--offlineserves from cache only; default cache dir (~/.cache/glint) used automatically with--offline— ✓ shipped v0.2.17;include: inputs:$[[ inputs.KEY ]]and$[[ inputs.KEY | default(…) ]]placeholders in fetched component YAML are substituted from the include'swith:block before parsing
Output formats — ✓ shipped v0.2.18
JSON (— ✓ shipped v0.2.18; machine-readable findings with stable schema (version 1)--format json)SARIF (— ✓ shipped v0.2.18; SARIF 2.1.0; consumed natively by GitHub Code Scanning and GitLab SAST--format sarif)JUnit XML (— ✓ shipped v0.2.18; lets CI pipelines publish lint results as a test report artifact--format junit)GitHub annotation format (— ✓ shipped v0.2.18; emits--format github)::error file=…,line=…,title=RULE::messagelines so findings appear as inline comments in PR diffs
Pipeline graph improvements
The SVG renderer and terminal tree cover the basic layout. These would bring it closer to GitLab's full interactive view.
Terminal job tree— ✓ shipped in v0.2.0 asglint graph tree; stages as branches, jobs as leaves, context-aware annotations— ✓ shipped post-v0.2.0; each include node shows the jobs it defines as dashed-arrow rounded nodes in a distinct styleglint graph includesshows jobs per file- Multi-job connector accuracy — draw one connector per job pair rather than one per stage pair in classic mode, so pipelines with uneven columns look correct
- Job tooltip / detail panel — embed a hidden
<title>and<desc>per chip so SVG viewers showstage,when,image, andneedson hover when: on_failurevisual distinction — dashed border or distinct icon for failure-path jobs- Blocked / skipped state colouring — grey out jobs that are statically unreachable given known
rules:conditions - Interactive HTML output — self-contained
.htmlfile with pan/zoom and a job-detail sidebar; no external dependencies - Mermaid pipeline output — keep
pipeline.gobut wire it up through--graph pipeline --format mermaidfor users who want to paste into mermaid.live
Findings quality — ✓ file and line numbers shipped post-v0.2.0; ruff-style format shipped v0.2.11
File and line numbers on findings — ✓ shipped post-v0.2.0; every finding includes the source file and exact line of the job key. Works across local includes, remote project templates, and fetched component templates.
Ruff-style output format — ✓ shipped v0.2.11; findings follow file:line: RULEID [severity] message matching the convention used by ruff and other modern linters.
Remaining improvements
— ✓ shipped post-v0.2.0; optional missing needs are downgraded toneeds: optional: truefalse-positive errors[WARNING]— ✓ shipped post-v0.2.0; jobs usingextends:jobs with missing script false errorsextends:that have noscriptafter resolution emit[WARNING](the script may come from an unfetchable remote base)rules:if:static reachability — report when a job's entirerules:block can never evaluate towhen: on_successgiven the declared pipeline variables (pure static, no context required)
CI / editor integration
- GitLab CI template — a
.gitlab-ci.ymlsnippet that runsglintas a pipeline-validation job before the real pipeline executes; publishable to the GitLab CI/CD Catalog - GitHub Actions action —
uses: k3nny/glint@v1wrapper for repositories that mirror or manage GitLab pipelines from GitHub - Pre-commit hook — entry for pre-commit so
glintruns automatically ongit commitwhen.gitlab-ci.ymlchanges - LSP server —
glint lspmode exposing diagnostics over the Language Server Protocol; enables inline squiggles in VS Code, JetBrains, Neovim, etc. without a dedicated extension - VS Code extension — thin wrapper around the LSP server with syntax highlighting for
.gitlab-ci.yml
Configuration — ✓ shipped v0.2.19
— ✓ shipped v0.2.19;.glint.ymlconfig fileignore:,severity:,stages:,token:,url:,cache_dir:; searched from the pipeline directory up to the git rootInline suppression comments— ✓ shipped v0.2.19;# glint: ignore GL007before a job definition; comma/space-separated rules;# glint: ignore allwildcard
Reliability and developer experience
Structured rule IDs— ✓ shipped post-v0.2.0; GL001–GL031 assigned; GL032 added v0.2.11; GL033 added v0.2.15; GL034–GL041 added v0.2.16; output formats (--format json/sarif/junit/github) added v0.2.18--explain <rule-id>— print the rule description, rationale, and an example fixSemantic versioning and first release— shipped asv0.1.0(2026-06-07)Subcommand CLI— shipped asv0.2.0(2026-06-11);glint check/glint graph [mode]with ruff-style--help- Changelog automation — generate release notes from Conventional Commits via
git-cliffor similar - Fuzz testing — add a
go test -fuzztarget for the YAML parser to harden it against malformed input