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.

Sign up for GitHub

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

Jump to bottom

[AutoRelease] t2-redis-2021-07-16-74903 #19843

Merged
merged 5 commits into from
Jul 21, 2021
Merged

[AutoRelease] t2-redis-2021-07-16-74903 #19843

merged 5 commits into from
Jul 21, 2021

Conversation

azclibot
Copy link
Contributor

@azclibot azclibot commented Jul 16, 2021 •
edited by RAY-316
Loading

SDKAuto and others added 3 commits July 8, 2021 06:00
CodeGen from PR 15117 in Azure/azure-rest-api-specs
1921050 
Cjf release0708 (Azure#15117)

* add tag into readme.go.md

* add tag to readme.go.md to release gosdk
version,CHANGELOG
8c175a5
test
b0099b4
@azclibot azclibot requested review from msyyc and RAY-316 as code owners July 16, 2021 02:54
@ghost ghost added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label Jul 16, 2021
@ghost
Copy link

ghost commented Jul 16, 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-redis-2021-07-16-74903(Do not merge) [AutoRelease] t2-redis-2021-07-16-74903 Jul 21, 2021
@RAY-316
Copy link
Contributor

RAY-316 commented Jul 21, 2021

/check-enforcer override

@msyyc msyyc merged commit 64128ba into Azure:main Jul 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@msyyc msyyc msyyc approved these changes

@RAY-316 RAY-316 Awaiting requested review from RAY-316

Assignees
No one assigned
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@azclibot @RAY-316 @msyyc