Labeler should search for labeler.yml AND labeler.yaml

[shadiramadan]

Description: YAML recommends .yaml as the preferred extension type: https://yaml.org/faq.html The Labeler action errors if the labeler file is created with .yaml. It should support both .yml and .yaml

Action version: Any/latest

Platform:

• [x] Ubuntu
• [x] macOS
• [x] Windows

Runner type:

• [x] Hosted
• [x] Self-hosted

Repro steps:
Use .yaml as the file extension.

Expected behavior: A description of what you expected to happen.

The action should support .yaml as if it was .yml

Actual behavior: A description of what is actually happening.

The config file was not found at .github/labeler.yml.

[gowridurgad]

Hi @shadiramadan, Thank you for reporting this issue. We will investigate it and get back to you as soon as we have some feedback.

[suyashgaonkar]

Hi @shadiramadan , currently, actions/labeler does not support YAML files. We will address this in future updates and are classifying this as a feature request for now

[mloskot]

@suyashgaonkar

currently, actions/labeler does not support YAML files

Could you clarify on this? I don't think you mean labeler.yml is not a YAML file 😕

Here is workaround I'm using with v4:

    - uses: actions/labeler@v5
      with:
        configuration-path: ".github/labeler.yaml"

[chiranjib-swain]

Hi @mloskot Thank you for bringing this up! To clarify, the actions/labeler action only recognizes the file named .github/labeler.yml by default. While both .yml and .yaml are valid YAML file extensions, the action specifically looks for .github/labeler.yml and does not automatically detect .yaml files or any other file names. If you wish to use a different filename or extension—such as .github/labeler.yaml—you'll need to explicitly specify the configuration path using the configuration-path input in your workflow. This allows flexibility in file naming, as you've observed. Supporting .yaml as an additional default option is a reasonable feature request and would enhance ease of use. We appreciate your suggestion and will consider it for future improvements. Thanks again for your feedback and for helping improve the tool!

[chiranjib-swain]

Hi @mloskot , Are there any further questions or concerns regarding this issue? If not, I’ll plan to close this ticket soon. Please let me know, thanks!

[mloskot]

Hi @chiranjib-swain , I don't have any more questions - I thumb-up'ed your answer a while ago. Thanks!