{CI} Update CODEOWNERS - #17313
Merged
Merged
Conversation
Collaborator
|
CODEOWNERS |
kairu-ms
approved these changes
Mar 16, 2021
msyyc
changed the title
Member
Author
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Contributor
|
If @ghost is a placeholder for non-owner files, please refer to the official document. A non-official explanation I can find is https://github.community/t/codeowners-file-with-a-not-file-type-condition/1423/5 YAML files can contain credentials which should be manually reviewed (#16795). |
3 tasks
msyyc
added a commit
that referenced
this pull request
Mar 24, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
if only .yml files of test are changed, there is no need to ask real codeowners to approve before merge the PR
Testing Guide
History Notes
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.