-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Add PRLabels to CODEOWNERS #19123
Add PRLabels to CODEOWNERS #19123
Conversation
Init - Add PRLabel to CODEOWNERS
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! 👍
I added a few entries. If this is what we need to get labels onto PRs, let's not wait for a complete list. Let's get started with what we have and then fill in later where needed.
I also have a question on this: is it possible to add an entry to CODEOWNERS that associates a label with a particular directory but NOT a code owner? I think that would be useful. |
Hi @mikekistler , I have tried it with CreateRuleFabricBot. The bot ignores the entry without code owner. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work!
Does our bot supports it (or it is a Github Action)?
Hi @weidongxu-microsoft, Yes, Fabric Bot supports it. |
@liurunliang this is step one of configuring the data then someone has to run the tool to generate the fabricbot config from this information. Is that something you plan to do separately? Perhaps we can do it in the same PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The general format looks good. Wes' comment above is an important one. This forms the basis that the rules can be generated from, but tooling will need to be run to extract the rules and merge them into the bot configuration in the repository.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a ton!
Relates to Azure/azure-sdk-tools#2743 |
Co-authored-by: Mike Kistler <mikekistler@microsoft.com>
Swagger Validation Report
|
Swagger pipeline restarted successfully, please wait for status update in this comment. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Co-authored-by: Mike Kistler <mikekistler@microsoft.com>
Hi @liurunliang, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
/specification/alertsmanagement/ @ofirmanor @olalavi @erangon @orieldar @ilaizi @shakednai1 @khaboasb @orenhor | ||
|
||
# PRLabel: %API Management | ||
/specification/apimanagement/ @promoisha @solankisamir |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ruowan @akning-ms unrelated to this PR but there are a lot of invalid users in this code owners file that we should figure out how to get fixed. Can you guys please file a clean-up item for tracking this issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We create a issue to track cleanup code owner files. Azure/azure-sdk-tools#3374
* Add PRLabels to CODEOWNERS Init - Add PRLabel to CODEOWNERS * Update CODEOWNERS Co-authored-by: Mike Kistler <mikekistler@microsoft.com> * Update CODEOWNERS Co-authored-by: Mike Kistler <mikekistler@microsoft.com> * Add fabricbot.json Co-authored-by: Ruoxuan Wang <52271048+ruowan@users.noreply.github.com> Co-authored-by: Mike Kistler <mikekistler@microsoft.com>
Init - Add PRLabel to CODEOWNERS
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following appy to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.