GitlabCI Support
What issues does this PR fix or reference?
This references the GitlabCI Support issue : https://github.com/redhat-developer/yaml-language-server/issues/972
Is it tested? How?
Tested on VsCode (vscode-yaml extension)
Details
Changelog
- Added
gitlabci.enabled/gitlabci.codelensEnabledoption -
!referencetags are not unknown ifgitlabci.enabledoption - Go-to definition for:
-
extendsnodes -
!referencetags (recursive: multiple definitions will be found if a job extends a job extending another job) -
needstags -
includenodes
-
- Show job hierarchy with mouse hover
- All files within all workspaces are parsed (for cross file references)
- “Show usages” code lens (with
gitlabci.codelensEnabledoption) which go to references to each job (used within needs and extends)
Screenshots
Go to includes (ctrl click on vscode)
Show / go to definitions for needs / !reference (ctrl hover / ctrl click on vscode)
Show job hierarchy with mouse hover
Show / go to definitions with extends (shows the recursive hierarchy)
Show usages code lens (when clicked)
This would be suuuuper useful !
coverage: 81.746% (-2.4%) from 84.174% when pulling 991f483e0edc84b538ca468333250932548f8baf on CelianR:celianr/gitlab-jump-to-definition into 0871dc12bb1d092bd08831dbe1f2179c41f55342 on redhat-developer:main.
Hi @msivasubramaniaan 👋 Do you have any feedback about this PR ? Tell me how you find this work / if some changes are necessary in order to be merged, this would be a great addition to the LSP in my opinion !