How to use multiple exclusions in FileMatchingPatterns?

[TemekRoman]

I'm trying to exclude the package-lock.json and packages.lock.json files in FileMatchingPatterns . However, I can't make the exclusion work.

The following excludes package-lock.json correctly:

FileMatchingPatterns: |
  **/*
  !**/package-lock.json

When I add the exclusion for packages.lock.json, all package-lock.json files are no longer excluded:

FileMatchingPatterns: |
  **/*
  !**/package-lock.json
  !**/packages.lock.json

I guess I'm missing something. Please advise.

[muiriswoulfe]

Hi @TemekRoman, thanks for using PR Metrics. I've taken a quick, provisional look and I think there might be an issue in the logic. I can definitely look into fixing this over the longer term. But I have a quick workaround for you now, to get you unblocked:

Using the following YAML should work:

FileMatchingPatterns: |
  **/*
  !**/{package-lock.json,packages.lock.json}

Let me know how you get on with this.

[muiriswoulfe]

I agree that it's definitely not great. I've got a fix for this out now at #373, but it'll be next week before I'm able to push it out to the Marketplace.

[TemekRoman]

In the overview.md, there is a link to AzureDevOps File matching patterns reference that explains how to use inclusions/exclusions. There is a section that features the double exclude.

Do you plan to support the double exclude as well?

[muiriswoulfe]

Makes sense. I've made some more updates to support this now.

[TemekRoman]

Awesome! Thanks a lot.

[muiriswoulfe]

The change is now available in v1.5.2, which was released a short while ago. Azure DevOps will likely pick up the latest version for you automatically but, if not, you can download it from the Marketplace.