-
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
[DoNotMerge] Add track2 config and fix sample #10415
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Swagger pipeline can not start as the pull request has merge conflicts. |
Azure Pipelines successfully started running 1 pipeline(s). |
Can one of the admins verify this patch? |
azure-sdk-for-go
|
azure-sdk-for-js
|
Azure CLI Extension Generation
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Trenton Generation
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-python
- Breaking Change detected in SDK
|
azure-sdk-for-net
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-python-track2
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
00Kai0
force-pushed
the
kaihuis-track2-containerregistry
branch
from
August 13, 2020 04:42
464c145
to
0c30e61
Compare
Azure Pipelines successfully started running 1 pipeline(s). |
azure-resource-manager-schemas
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
Azure Pipelines successfully started running 1 pipeline(s). |
00Kai0
added
DoNotMerge
<valid label in PR review process> use to hold merge after approval
and removed
Do Not Merge
labels
Aug 19, 2020
* Update Resources 2020-06 to include changes from 2019-10 (From PR - Azure#9441) * Update Resources 2020-06 to include changes from 2019-10 (From PR - Azure#9580) * Rollback java support for Resources API version 2020-06-01
00Kai0
force-pushed
the
kaihuis-track2-containerregistry
branch
from
October 12, 2020 07:48
5e42e00
to
e001e1a
Compare
00Kai0
requested review from
dkulkarni-ms,
grizzlytheodore,
haagha,
hectorhdzg,
hyonholee,
kjeur,
madewithsmiles,
markwolff,
matthchr,
MehaKaushik,
MS-syh2qs,
novinc,
ofirmanor,
orieldar,
rajkumar-rangaraj,
ramthi,
reyang,
Sandido,
shurd,
solankisamir,
stankovski,
TimothyMothra,
wilcobmsft,
xingwu1 and
yangyuan
as code owners
October 12, 2020 07:48
Pull request contains merge conflicts. |
wrong pr :( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
CI-BreakingChange-Python
Container Registry
DoNotMerge
<valid label in PR review process> use to hold merge after approval
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.