-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update output-folders to generate in _generated. #16685
Conversation
Hi, @tjprescott Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com |
Swagger Validation Report
|
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
Swagger Generation Artifacts
|
Hi @tjprescott I am fine with the change but the pipeline is failing to generate the SDK, is that ok? |
Yeah, trying to get to the bottom of that one. It definitely does generate. I love CI... |
616b4c8
to
bc850a1
Compare
Azure/azure-sdk-for-python#21737 Per discussion with @msyyc, the |
I think this pipeline will pass once you have committed your first version of each SDK to the Python SDK repo. |
* Update output-folders to generate in _generated. * Remove _generated annotation from Creator. * Include _generated only on updates, not create.
This change to the readmes will allow you to generate your _generated folder while leaving any custom written code in-place.