6 Commits

Include renames

Author	SHA1	Message	Date
k3nnyandClaude Sonnet 4.6	8c3605ed52	feat(cli): colorized, columnized text output with line:col locations ... Replace the per-line fmt.Println loop with writeTextFindings() in cmd/glint/output.go. The new renderer: - Aligns all findings into four space-separated columns: location, rule ID, severity, message — widths computed from the full finding set so all lines are flush - Colors severity words when stdout is a TTY and NO_COLOR is not set: red+bold for "error", orange+bold for "warning"; location dimmed; rule ID bold - Formats location as file:line:col when column is known, file:line otherwise, falling back to just file To populate column numbers, add Column int to model.Job (set from keyNode.Column in the YAML parser) and Finding.Column (set during the checkJob source-location attachment pass and in the ten cross-job check sites that explicitly set Line: job.Line). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-26 22:13:52 +02:00
k3nnyandClaude Sonnet 4.6	416659ffd8	feat(linter): context-scoped needs:/dependencies: cross-checks ... When glint check runs in single-context mode (--branch, --tag, --source, or --var), jobs that resolve to JobSkipped against that context are now excluded from needs: and dependencies: cross-job checks (GL027-GL031). This eliminates false-positive errors for jobs intentionally gated to specific pipeline events (e.g. a deploy job with rules:if: CI_COMMIT_TAG no longer triggers GL027 on branch pipelines). linter.Lint now accepts a skipped map[string]bool (nil = check all jobs); checkNeeds and checkDependencies skip jobs present in the map. Multi-context mode (--context) passes nil, so all jobs are checked regardless of context. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-25 00:25:09 +02:00
k3nnyandClaude Sonnet 4.6	f48bf02152	feat(linter): add structured rule IDs (GL001–GL031) ... Every Finding now carries a stable Rule string field with a GL### code. The ID appears in output between the source location and the message: [ERROR] job "deploy" (ci.yml:14) GL003: missing required field 'script' [WARNING] (ci.yml) GL001: no stages defined Rules: GL001 no-stages GL002 workflow-when GL003 missing-script GL004 unknown-stage GL005 only-rules-conflict GL006 except-rules-conflict GL007 deprecated-only GL008 invalid-when GL009 delayed-no-start-in GL010 start-in-no-delayed GL011 invalid-parallel GL012 invalid-retry GL013 invalid-retry-when GL014 invalid-allow-failure GL015 invalid-interruptible GL016 trigger-with-script GL017 invalid-trigger GL018 invalid-coverage GL019 invalid-release GL020 invalid-environment GL021 invalid-artifacts GL022 pages-public GL023 invalid-cache GL024 invalid-rules-when GL025 invalid-image GL026 invalid-inherit GL027 needs-unknown GL028 needs-stage-order GL029 needs-cycle GL030 unknown-dependency GL031 dependency-stage Changes: - internal/linter/rules.go: new file with all 31 constants + doc comments - linter.Finding: add Rule string field; String() inserts it before the message colon when non-empty; format unchanged when Rule == "" - All Finding{} literals in linter.go, keywords.go, needs.go, dependencies.go updated with the correct Rule: constant - README.md lint rules table: new ID column added to all four sections - CHANGELOG.md: entry in [Unreleased] Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-11 22:56:24 +02:00
k3nnyandClaude Sonnet 4.6	a303f63a5e	feat(linter): add file/line to findings; downgrade extends missing-script to warning ... Every finding now carries the source file and exact line number of the job key in its YAML file. Format: [ERROR] job "name" (file.yml:12): message. Pipeline-level findings (workflow rules, no stages) reference p.SourceFile. Cross-file include jobs (local, project, component) carry the include source as their File, set via Pipeline.SetJobOrigin after each ParseBytes call in the resolver. Line numbers come from the yaml.Node key node (exact job-name line) in a new document-level first pass in ParseBytes, replacing the previous map[string]yaml.Node approach which only gave value-node lines. Also: jobs that declare extends: but have no script after resolution now emit WARNING instead of ERROR. The script may come from a base in a remote include that was not fetched (no token, offline), making the error a false positive in common project setups. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-11 21:24:18 +02:00
k3nny	51b3e1f297	fix(project): rename tool to glint	2026-06-10 22:40:42 +02:00
k3nny	e2334ec12d	feat(gitlab-sim): ✨ first commit	2026-06-05 01:29:07 +02:00