Skip to content

Comments

[AutoRelease] t2-confidentialledger-2021-04-28-37493#18377

Closed
azclibot wants to merge 3 commits intoAzure:masterfrom
azclibot:t2-confidentialledger-2021-04-28-37493
Closed

[AutoRelease] t2-confidentialledger-2021-04-28-37493#18377
azclibot wants to merge 3 commits intoAzure:masterfrom
azclibot:t2-confidentialledger-2021-04-28-37493

Conversation

@azclibot
Copy link
Contributor

@azclibot azclibot commented Apr 28, 2021

SDKAuto and others added 2 commits April 27, 2021 03:44
[python] t2-confidentialledger config (Azure#14144)

* Update readme.python.md

* Update readme.python.md
@ghost ghost added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label Apr 28, 2021
@ghost
Copy link

ghost commented Apr 28, 2021

Thank you for your contribution azclibot! We will review the pull request and get back to you soon.

@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

@RAY-316 RAY-316 changed the title [AutoRelease] t2-confidentialledger-2021-04-28-37493(Do not merge) [AutoRelease] t2-confidentialledger-2021-04-28-37493 Apr 28, 2021
@RAY-316
Copy link
Contributor

RAY-316 commented Apr 28, 2021

/check-enforcer override

@RAY-316
Copy link
Contributor

RAY-316 commented Apr 28, 2021

new update in readme.python

@RAY-316 RAY-316 closed this Apr 28, 2021
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-python that referenced this pull request Apr 11, 2022
Update costmanagement.pricesheets.json (Azure#18377)

* Update costmanagement.pricesheets.json

* Update costmanagement.pricesheets.json
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

customer-reported Issues that are reported by GitHub users external to the Azure organization.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants