CI does not warn that a merge containing a new folder will break the build

[danieljurek]

A change that introduced a new folder in the .NET Repo (Azure/azure-sdk-for-net#6652) has resulted in build breaks during the "Verify Readmes" step in the Scheduled Build Analyze step.

While the issue was quickly mitigated by adding an exclusion to the readme verifier we should consider a broader fix or a way to find out that we'll have this problem in CI.

[danieljurek]

Quick fix: https://github.com/Azure/azure-sdk-for-net/pull/6924/files

[danieljurek]

Spoke w/ @scbedd about this. We have a plan for fixing this:

• Create README.md files for each of the Smoke Tests with all of the sections in place
• Use a title like "Azure Smoke Tests for <language>"
• Add ...|Azure Smoke Tests for Python (where the ... is the preexisting regex) to the title regex in the appropriate .docsettings.yml file (e.g. https://github.com/Azure/azure-sdk-for-js/blob/master/.docsettings.yml)

The readme verifier was designed to find errors and should be extended to work with additional scenarios.

In the short term, to get these tests running for PRs /azp run command to kick off the appropriate language client build (e.g. /azp run net - client

[github-actions]

Hi @danieljurek, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.