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

Bump stress-test-addons chart version to 0.1.7 #2042

Merged
1 commit merged into from
Sep 27, 2021

Conversation

benbp
Copy link
Member

@benbp benbp commented Sep 27, 2021

Updating stress-test-addons helm chart version with changes from #2039

@benbp benbp requested a review from a team as a code owner September 27, 2021 19:08
@benbp benbp added the Central-EngSys This issue is owned by the Engineering System team. label Sep 27, 2021
@benbp benbp self-assigned this Sep 27, 2021
@ghost
Copy link

ghost commented Sep 27, 2021

Hello @benbp!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@check-enforcer-staging
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).

@benbp
Copy link
Member Author

benbp commented Sep 27, 2021

/check-enforcer override

@ghost ghost merged commit 4849d89 into Azure:main Sep 27, 2021
@benbp benbp deleted the benbp/stress-test-addons-0.1.7 branch September 27, 2021 22:29
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Central-EngSys This issue is owned by the Engineering System team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants