5 Commits

Include renames

Author	SHA1	Message	Date
k3nnyandClaude Sonnet 4.6	04f17f8616	test(coverage): add unit tests across all packages; remove dead code ... - Added comprehensive table-driven test suites for all packages: cmd/glint, cicontext, fetcher, graph, linter, model, resolver. Coverage reaches 98%+ statement coverage across the codebase. - Replaced os.Exit calls in cmd/glint with an `exit` variable so tests can capture exit codes without terminating the test process. - Removed unreachable code found during coverage analysis: dead guard in cicontext.parseRegexLiteral; dead len(jobs)==0 branch in graph.Pipeline; skipWin struct field and dead continue in graph.convertToPNG; pipelineSVG return type simplified to string. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-14 22:03:46 +02:00
k3nnyandClaude Sonnet 4.6	5fee51ec7d	fix(cli): consistent output format, sorted findings, version flag ... - Workflow rules now use strict if: evaluation (parse failure → skip rule, not match); fixes premature matching that blocked later rules and injected wrong variables into the context - Single = accepted as alias for == in rules:if: expressions - File/Line preserved through extends: resolution (lost during YAML encode/decode round-trip in the resolver) - Findings sorted by (File, Line, Rule) so same-file issues group together - All warnings use ruff-style path: [warning] message format (includes, extends chains, workflow non-start) - Add --version / -v flag; version shown at top of every --help output - Build injects version via ldflags using git describe Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-13 00:13:51 +02:00
k3nnyandClaude Sonnet 4.6	a0e2582cf1	fix(linter): support bare true/false and integer literals in rules:if: ... GitLab CI expressions allow unquoted true, false, and integers as comparison operands (all treated as their string representations): $GATEWAY_ENABLED == true (equivalent to == "true") $FEATURE_FLAG == false (equivalent to == "false") $PARALLEL == 4 (equivalent to == "4") $ENABLED == 1 / == 0 Previously these fell through to permissive true because parseValue only recognised $VAR, "${VAR}", quoted strings, and null. Added: - true/false keyword branch → returns "true"/"false" - integer literal branch (digits only) → returns decimal string All three new forms are correctly excluded from longer identifier prefixes (identByte boundary check). Adds 8 new unit tests. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-11 22:20:59 +02:00
k3nnyandClaude Sonnet 4.6	e931b9d1c9	fix(linter): improve rules:if: expression evaluator ... Four correctness fixes to the GitLab CI expression parser in internal/cicontext/eval.go: - Multi-line: \n and \r are now treated as whitespace in skipWS so block-scalar or folded-scalar if: values with || / && on continuation lines evaluate correctly instead of falling back to permissive true. - ${VAR} curly-brace variable syntax now supported in parseValue. - Regex flags (/pattern/i, /pattern/m, /pattern/s) are now consumed and translated to Go (?i)/(?m)/(?s) prefixes via applyRegexFlags. - Variable on RHS of =~ / !~: when the right operand is $VAR, the variable's value is interpreted as a /regex/[flags] string via extractRegexFromString; non-regex values fall back to permissive true. Adds 16 new unit tests covering all four cases and a testdata fixture (rules_if_expr.yml) exercising multi-line, ${VAR}, and /pattern/i in a real pipeline with context flags. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-11 22:08:08 +02:00
k3nny	f98e9c42e7	feat(gitlab-sim): 🚀 branches support	2026-06-07 23:13:52 +02:00