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

tools: Don't only require FFAPI reviews for report changes in specific directories #22278

Merged

Conversation

Josmithr
Copy link
Contributor

@Josmithr Josmithr commented Aug 20, 2024

Don't require API reviews for API report changes in /tools packages. Also simplify specification patterns for CODEOWNERS, and...

  • Require fluid-cr-infra review for API changes in /build-tools packages
  • Require fluid-cr-server review for API changes in /server packages

@github-actions github-actions bot added area: build Build related issues base: main PRs targeted against main branch labels Aug 20, 2024
@Josmithr Josmithr marked this pull request as ready for review August 21, 2024 17:42
@Josmithr Josmithr requested a review from a team as a code owner August 21, 2024 17:42
@Josmithr Josmithr requested a review from a team August 21, 2024 18:25
@Josmithr Josmithr merged commit ecd6063 into microsoft:main Aug 21, 2024
28 checks passed
@Josmithr Josmithr deleted the build/don't-require-reviews-for-tools branch August 21, 2024 18:33
Comment on lines +55 to +58
/**/api-report/*.api.md @microsoft/fluid-cr-api
/build-tools/**/api-report/*.api.md @microsoft/fluid-cr-infra
/server/**/api-report/*.api.md @microsoft/fluid-cr-server
/tools/**/api-report/*.api.md # Do not require API review for tools packages
Copy link
Contributor

Choose a reason for hiding this comment

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

@Josmithr we shouldn't add ownership to groups unless they explicitly opt into it, so adding cr-infra, and cr-server shouldn't be done unless those groups know and agree to the requirements they are signing up for, to review all changes. it might be a better change to just limit cr-api to the packages directory, rather than creating new layers of ownership

Copy link
Contributor

Choose a reason for hiding this comment

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

i would expect some members of those teams to sign off here, to signify that they know and agree to the requirements.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fair. I can put up a PR to revert those changes.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Josmithr added a commit that referenced this pull request Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: build Build related issues base: main PRs targeted against main branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants