feat(graph): show jobs per file in include dependency graph
Each node in 'glint graph includes' now lists the jobs defined directly in that file. Jobs appear as rounded Mermaid nodes with a distinct light-purple style, connected with dashed arrows (-.->). This visual distinction separates ownership (file -.-> job) from the include hierarchy (file --> included-file). The root file's jobs are collected by re-parsing it without include resolution; local and fetched project/component nodes populate their job list in the existing recurse* methods. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -7,6 +7,10 @@ This project uses [Semantic Versioning](https://semver.org).
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
### Added
|
||||
|
||||
- **`glint graph includes` shows jobs per file** — each node in the Mermaid include dependency graph now shows the jobs defined directly in that file. Jobs are rendered as rounded nodes (`(name)`) in a distinct light-purple style, connected with dashed arrows (`-.->`) to distinguish ownership from the include hierarchy (solid `-->` arrows). The root pipeline file always shows its direct jobs; local and fetched project/component nodes show theirs when the file can be read.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **Variable map form now parses correctly** — `variables:` entries that use the extended `{value, description, options}` form (GitLab CI 13.7+) no longer cause `yaml: cannot unmarshal !!map into string`. Both `Pipeline.Variables` and per-job `Variables` now accept either plain strings or map-form declarations.
|
||||
|
||||
Reference in New Issue
Block a user