Could we also take the opportunity to remove the dot in ".pipelines"? That is really confusing at it looks to user like a derived folder more than part of source control, and does not appear in some UIs. I don't see the point of "hiding" the pipelines in a project whose very focus is devops.

@dtzar @jotaylo thoughts on @algattik's suggestion? I wasn't sure if there was a reason we used a '.'

@jotaylo created a temporary pipeline to test the PR, the passing job is at https://aidemos.visualstudio.com/MLOps/_build/results?buildId=3966

@algattik @tcare .pipelines folder was used because this was a similar folder structure used for other similar orchestrator pipeline products. i.e. Github workflows uses .github\workflow CircleCI uses .circleci

I agree though that .pipelines is ambiguous. The official name for these are "Azure Pipelines" although a folder like .azurepipelines or .azure I'm not sure is any better. Open to other ideas, but IMO all the pipelines orchestration should be contained in a folder at the root. Not stuck on the . at the start, although I like this puts the folder at the top of the order and as mentioned it seems to be a common pattern.

We'll merge for now and can do another PR if we feel strongly about changing the folder.

Pipelines have all been updated, let me know if you see issues :)