-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Update local_auth_darwin CODEOWNERS #10074
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
Conversation
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.
Code Review
This pull request adds @okorohelijah as a code owner for the local_auth_darwin package. The change is functionally correct, but I have a suggestion to improve maintainability by sorting the code owners alphabetically. Additionally, please note that the pull request title does not follow the repository's contribution guidelines. The title should be updated to start with the package name in square brackets, for example: [local_auth_darwin] Update CODEOWNERS.
| packages/image_picker/image_picker_macos/** @vashworth @louisehsu | ||
| packages/in_app_purchase/in_app_purchase_storekit/** @louisehsu @LongCatIsLooong | ||
| packages/local_auth/local_auth_darwin/** @vashworth | ||
| packages/local_auth/local_auth_darwin/** @vashworth @okorohelijah |
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.
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.
Sorting by unofficial "primary" and "secondary" even though the tooling doesn't enforce it.
okorohelijah
left a comment
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.
LGTM
flutter/packages@117bf63...389c678 2025-09-25 magder@google.com Update local_auth_darwin CODEOWNERS (flutter/packages#10074) 2025-09-25 10687576+bparrishMines@users.noreply.github.com [interactive_media_ads] Adds support for time offsets of ad breaks (flutter/packages#9953) 2025-09-25 engine-flutter-autoroll@skia.org Roll Flutter from 4a04204 to b1a28bc (44 revisions) (flutter/packages#10077) 2025-09-24 jason-simmons@users.noreply.github.com [google_fonts] Make a map keyed on FontWeight non-const (flutter/packages#10058) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages-flutter-autoroll Please CC flutter-ecosystem@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Add @okorohelijah to CODEOWNERs.
Pre-Review Checklist
[shared_preferences]pubspec.yamlwith an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under1.CHANGELOG.mdto add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under1.///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2 ↩3