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

Update CODEOWNERS: add all azure-spring developers. #23446

Merged

Conversation

chenrujun
Copy link

Update CODEOWNERS: add all azure-spring developers.

@chenrujun chenrujun self-assigned this Aug 10, 2021
@chenrujun chenrujun added this to the [2021] September milestone Aug 10, 2021
@chenrujun chenrujun added the azure-spring All azure-spring related issues label Aug 10, 2021
@chenrujun
Copy link
Author

Hi, @saragluna , @zhichengliu12581 , @ZhuXiaoBing-cn , @moarychan , @michaelqi793 .
Please help to review this PR.

@chenrujun chenrujun force-pushed the update-CODEOWNERS-for-spring-related-folders branch from 276458c to 6f08dd0 Compare August 10, 2021 03:27
@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 java - [service] - ci

Copy link
Member

@yiliuTo yiliuTo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@chenrujun
Copy link
Author

/check-enforcer override

@chenrujun chenrujun merged commit 404eda8 into Azure:main Aug 11, 2021
@chenrujun chenrujun deleted the update-CODEOWNERS-for-spring-related-folders branch August 11, 2021 02:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
azure-spring All azure-spring related issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants