Skip to content
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

[Issue helper] Skip issue created by owners #23165

Merged
merged 18 commits into from
Feb 22, 2022
Merged

Conversation

BigCat20196
Copy link
Contributor

No description provided.

@msyyc msyyc changed the title [Issue helper] Skip self creater [Issue helper] Skip issue created by owners Feb 22, 2022
@check-enforcer
Copy link

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run python - [service] - ci

@msyyc
Copy link
Member

msyyc commented Feb 22, 2022

/check-enforcer override

@msyyc msyyc merged commit 16bbcef into Azure:main Feb 22, 2022
rakshith91 pushed a commit to rakshith91/azure-sdk-for-python that referenced this pull request Apr 10, 2022
* initial

* rename yml

* git push function

* only collect issues with label 'Mgmt'

* handle exception

* date format

* update log print

* update bot policy

* skip self-create issue

* add ziwei and zhenbiao

* Update python.py

* skip self author

* skip self author

* skip self author

* Update python.py

* Update python.py

Co-authored-by: msyyc <70930885+msyyc@users.noreply.github.com>
Co-authored-by: Yuchao Yan <yuchaoyan@microsoft.com>
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-python that referenced this pull request Apr 18, 2023
Release machinelearningservices microsoft.machine learning services 2023 04 01 preview (Azure#23449)

* Adds base for updating Microsoft.MachineLearningServices from version preview/2023-02-01-preview to version 2023-04-01-preview

* Updates readme

* Updates API version in new specs and examples

* [Preview] Bring Back Scheduled Shutdown MLC models (Azure#23040)

* [Preview] Bring Back Scheduled Shutdown MLC models

* update example json

---------

Co-authored-by: Naman Agarwal <naagarw@microsoft.com>

* add minLength:1 prop to required strings (Azure#23108)

* add parameter enableDataIsolation to workspace properties (Azure#23061)

* add parameter enableDataIsolation to workspace properties

* minor change to re-run the test pipelines

* minor comment change to trigger the test pipeline again

---------

Co-authored-by: Mingwei He <mingweihe@microsoft.com>

* expose connection expiryTime in 2023-04-01-preview swagger (Azure#23118)

* Add Workspace Managed Network Swagger (Azure#23283)

* add managed network swagger

* fix validation errors

* address ARM comments

* fix example

* do not flatten outbound rules, need nested props

---------

Co-authored-by: Josh Harrington <joharrington@microsoft.com>

* Add Registries 2023-04-01-Preview Swagger (Azure#23163)

* x

* fix spellcheck

* update preview examples

* update examples

* fix for swagger modelvalidation gate

* examples should be in camelCase

* more fixes for pr gates

* fix syntax

* add registryNameParameter

* addressing comments

* fix one more location property

* address comments

* update PrivateEndpointConnectionProperties

* git didn't push all of my changes

* fix circular dependency

* update

* PATCH operation should have sku, identity properties

---------

Co-authored-by: Komal Yadav <komalyadav@microsoft.com>

* MFE April-preview 2023 staging (Azure#23165)

* update mfe.json to latest

* update preview examples

* make it pretty

* createOrUpload example touch-ups

* pretty check

* POST pendingUpload lint violation, description, and array

* spell check fixes

* featurestore updates + notification patch updates to align with jobs

* fix feature examples

* rename PendingUpload -> startPendingUpload + better description

* prettier feature get/list.json

* update Job-Update example

* update descriptions

* x-ms-secret-true, remove wasbs and pattern for registries

* update examples to remove wasbsUri

* update registry refrence and add pattern to featuresetname

* temporarily add in registry reference

* one more pattern add-on for featuresetname

* remove wasbs since that is no longer a part of PR

* bump

* add empty secrets to examples - can show object but hide secret itself

* original-uri -> azure-async-operation

* createOrGetPendingUpload -> createOrGetStartPendingUpload

* add ms-secret to uri to keep it from breaking relative to GA

---------

Co-authored-by: Kayla Ames <kaseager@microsoft.com>

* [HUB] update team configuration related properties (Azure#23285)

* [HUB] update team configuration related properties

* Update description

* fix merge issue

* update workspace get operation example with managenetwork included (Azure#23411)

* custom words merge

* swap to original-uri

* v5->v3

* registryRenames

* mlc update to align with v3 types

* finish updating examples

---------

Co-authored-by: Naman Agarwal <namanag16@gmail.com>
Co-authored-by: Naman Agarwal <naagarw@microsoft.com>
Co-authored-by: Teddy Todorov <thtodoro@microsoft.com>
Co-authored-by: Ming <hemingwei2017@gmail.com>
Co-authored-by: Mingwei He <mingweihe@microsoft.com>
Co-authored-by: jiewe <127981966+jiewe@users.noreply.github.com>
Co-authored-by: Josh Harrington <53531213+joshharrin@users.noreply.github.com>
Co-authored-by: Josh Harrington <joharrington@microsoft.com>
Co-authored-by: Komal Yadav <23komal.yadav23@gmail.com>
Co-authored-by: Komal Yadav <komalyadav@microsoft.com>
Co-authored-by: Kayla Ames <kaseager@microsoft.com>
Co-authored-by: ZhidaLiu <zhili@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants