You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks very much for having taken some time to put together your devops-centered blog posts. They have been instrumental in helping me level-up my Azure DevOps!
I'm reaching out today wondering if something is either out of date or place regarding path wildcards. The official MS docs state:
In your example, you're using a wild card with your paths. Has Microsoft changed its implementation since you've written your blog post?
I realize that this is a bit of a random question, but I'm hoping you can shed some light on this, as getting the path includes / excludes right (and actually triggering) is critical for monorepos.
Thanks again!
The text was updated successfully, but these errors were encountered:
Hi Julie,
Thanks very much for having taken some time to put together your devops-centered blog posts. They have been instrumental in helping me level-up my Azure DevOps!
I'm reaching out today wondering if something is either out of date or place regarding path wildcards. The official MS docs state:
"Wild cards are not supported with path filters."
source - https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/azure-repos-git?view=azure-devops&tabs=yaml#paths
In your example, you're using a wild card with your paths. Has Microsoft changed its implementation since you've written your blog post?
I realize that this is a bit of a random question, but I'm hoping you can shed some light on this, as getting the path includes / excludes right (and actually triggering) is critical for monorepos.
Thanks again!
The text was updated successfully, but these errors were encountered: