Lint the shell inside your .gitlab-ci.yml
Every script:, before_script: and after_script: in your
pipeline is a shell script nobody lints. Drop in your CI YAML and see ShellCheck's findings for each one —
unquoted variables, broken tests, silent failures — worked out in this browser tab.
1. Your CI YAML
Drop
.gitlab-ci.yml and any included YAML here, or click to browse.
Several files at once is fine; each is linted. Up to 2 MB each. Read in this tab only.
Every
.yml/.yaml file in it is linted; nothing else is read.include: remote:, project: and component:
content is not fetched, and !reference values are skipped (GitLab resolves them on its side) —
add those files here yourself if you want them linted.
2. Options
ShellCheck's dialects. Most GitLab images run
bash or sh.
Results Sample data
Loading the engine…
Summary
Script blocks
–
Findings shown
–
Errors · warnings
–
Add CI YAML, or load the sample, to see results here.
Plain-language summary
Pipelines doing things nobody expected? ReleaseTEAM untangles GitLab CI/CD for teams of every size.
Talk to ReleaseTEAM about your pipelines