[Synapse] split artifacts swaggers per operation groups#15513
[Synapse] split artifacts swaggers per operation groups#15513lmazuel merged 12 commits intoAzure:mainfrom
Conversation
|
Hi, @idear1203 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 |
|
[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 pipeline restarted successfully, please wait for status update in this comment. |
ghost
added
the
|
Hi @idear1203, Your PR has some issues. Please fix the CI sequentially by following the order of
|
|
Hi, @idear1203. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
idear1203
force-pushed
the
synapse_split_artifacts_swaggers_to_operation_groups
branch
from
4e4821d to
b17d572
Compare
idear1203
force-pushed
the
synapse_split_artifacts_swaggers_to_operation_groups
branch
from
2dc9e55 to
b7bf996
Compare
openapi-pipeline-app
bot
added
CI-FixRequiredOnFailure
and removed
CI-FixRequiredOnFailure
labels
idear1203
force-pushed
the
synapse_split_artifacts_swaggers_to_operation_groups
branch
2 times, most recently
from
d31c971 to
806b18b
Compare
|
NewApiVersionRequired reason: |
|
Hi @idear1203, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
openapi-pipeline-app
bot
added
CI-BreakingChange-Go
and removed
CI-FixRequiredOnFailure
NewApiVersionRequired
labels
idear1203
force-pushed
the
synapse_split_artifacts_swaggers_to_operation_groups
branch
from
900bdcd to
88d760a
Compare
idear1203
force-pushed
the
synapse_split_artifacts_swaggers_to_operation_groups
branch
from
7dcea95 to
4335ee3
Compare
* [Synapse] - split kqlScripts * Run code style checker * Split artifacts per operation groups * Update readme and solve reference issues * linkedservice to linkedService * linkedservice to linkedService more * Resolve conflicts * Split 2020-12-01 * Fix syntax issue * Remove operations.json from reamd * readme Minor fix * lenient-model-deduplication Co-authored-by: Dongwei Wang <dongwwa@microsoft.com>
2 participants
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit (including refactoring) and then push new changes, including version updates, in separate commits.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.