Frontend: Update icon when users configured .gitlab-ci.yaml as a default
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
The CI/CD pipeline only recognizes the .yml extension for the .gitlab-ci file.
It should also recognize a .yaml extension since it as also a valid extension for a YAML file.
Steps to reproduce
- Add a valid .gitlab-ci.yaml file to a repository
- Observe that no CI/CD pipeline is detected
- Rename .gitlab-ci.yaml to .gitlab-ci.yml
- Observe that the CI/CD pipeline is now detected
What is the current bug behavior?
No CI/CD pipeline is created for a valid .gitlab-ci.yaml file
What is the expected correct behavior?
CI/CD pipeline should be created for .yaml file (same as if it were .yml)
Proposal
Since a file matcher is used in some frontend components to detect the .gitlab-ci.yml file, it would need to provide similar support for .gitlab-ci.yaml as well. The pipeline editor would also need to treat the .gitlab-ci.yaml file the same way that the .gitlab-ci.yml file is handled as well.
This issue about removing instances where we manually match and use the ruby helper that is a general recommendation here.
Output of checks
This happens on GitLab.com