Open SunBlack opened 3 years ago
Some files were created manually, and others were created by azure/GitHub. The auto created files are yml and others are yaml
While it would be nice to only have either yml or yaml extensions, I don't see a big problem with mixing them. However, changing the extensions (renaming the files) now might lead to some headaches (files not found etc). FUNDING.yml, config.yml, and stale.yml indeed seem to only work with the yml extension, not the yaml extension. In contrast to that, yaml is the officially recommended extension. As a compromise, we could check whether we can change env.yml to env.yaml. Then we would use the yaml extension everywhere except for the GitHub files
For a PR, I first searched for all file extensions used by PCL:
After calling this command, you will see that there are files with
yaml
andyml
as extension. In general: Both extensions are correct for YAML, but nevertheless I think we should unify it.Find all YAML files
Result:
For example, is there a reason why
env.yml
hasyml
as file extension butformatting.yaml
hasyaml
?As the Github names seems to have fixed extensions I suggest to use always
yml
for all YAML files.