SchemaStore / SchemaStore/schemastore
Wrong detection of gitlab-ci.yml scheme
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 2.3k
- Avg merge
- 20h 23m
- Merged PRs (30d)
- 124
Description
Area with issue?
JSON Schema
✔️ Expected Behavior
Visual Studio Code (with Red Hat YAML extention) should automatically detect that the schema for the .gitlab-ci.yml file.
❌ Actual Behavior
Visual Studio Code apply for every YAML file the F-Droid metadata scheme. I added some screenshots.
Bildschirmfoto vom 2021-08-06 09-57-55
Bildschirmfoto vom 2021-08-06 09-58-06
YAML or JSON file that does not work.
stages:
- test
golangci-lint:
stage: test
before_script:
- docker rm --force $(docker ps --all --quiet) || true
- docker network rm $(docker network ls --quiet) || true
- docker volume rm $(docker volume ls --quiet) || true
script:
- make container-run/golangci-lint
after_script:
- docker rm --force $(docker ps --all --quiet) || true
- docker network rm $(docker network ls --quiet) || true
- docker volume rm $(docker volume ls --quiet) || true
except:
- tags@orbis-u/uctl-cluster
gosec:
stage: test
before_script:
- docker rm --force $(docker ps --all --quiet) || true
- docker network rm $(docker network ls --quiet) || true
- docker volume rm $(docker volume ls --quiet) || true
script:
- make container-run/gosec
after_script:
- docker rm --force $(docker ps --all --quiet) || true
- docker network rm $(docker network ls --quiet) || true
- docker volume rm $(docker volume ls --quiet) || true
except:
- tags@orbis-u/uctl-cluster
markdown-lint:
stage: test
before_script:
- docker rm --force $(docker ps --all --quiet) || true
- docker network rm $(docker network ls --quiet) || true
- docker volume rm $(docker volume ls --quiet) || true
script:
- docker run --rm --volume $(pwd):/work docker.io/tmknom/markdownlint:0.23.1 *.md
after_script:
- docker rm --force $(docker ps --all --quiet) || true
- docker network rm $(docker network ls --quiet) || true
- docker volume rm $(docker volume ls --quiet) || true
except:
- tags@orbis-u/uctl-cluster
unit:
stage: test
before_script:
- docker rm --force $(docker ps --all --quiet) || true
- docker network rm $(docker network ls --quiet) || true
- docker volume rm $(docker volume ls --quiet) || true
script:
- make container-run/test/unit
after_script:
- docker rm --force $(docker ps --all --quiet) || true
- docker network rm $(docker network ls --quiet) || true
- docker volume rm $(docker volume ls --quiet) || true
except:
- tags@orbis-u/uctl-cluster
IDE or code editor.
Visual Studio Code
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in Visual Studio Code with the Red Hat YAML extension using the provided .gitlab-ci.yml example. Trace how the repository associates schemas with YAML filenames and verify why the F-Droid metadata schema is selected. Done means .gitlab-ci.yml receives the expected GitLab CI schema without changing schema detection for other YAML files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode, yaml
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100