Skip to content
Discussion options

You must be logged in to vote

Thanks for raising the issue @EmilMagenta, it’s kind of funny that no one pointed it out before 😄

I actually agree we should support both .yml and .yaml.

Technically, only .yml is correct for publiccode files and matches the project name as @jgroenen said, but as you said people are already using .yaml in some repos and it's actually a pretty reasonable assumption for users to think .yaml would work. It's not a big effort for the crawler to check both extensions.

We could prioritize .yml for consistency and backward compatibility (for example, if they both exist in the same repo), but still handle .yaml as a valid option.

Replies: 3 comments 2 replies

Comment options

You must be logged in to vote
1 reply
@EmilMagenta
Comment options

Comment options

You must be logged in to vote
1 reply
@jgroenen
Comment options

Comment options

You must be logged in to vote
0 replies
Answer selected by EmilMagenta
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
4 participants