-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[PM-28487] Move Events and EventsProcessor to DIRT ownership #6678
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
base: main
Are you sure you want to change the base?
[PM-28487] Move Events and EventsProcessor to DIRT ownership #6678
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6678 +/- ##
==========================================
- Coverage 53.63% 53.63% -0.01%
==========================================
Files 1926 1926
Lines 85717 85711 -6
Branches 7686 7686
==========================================
- Hits 45978 45974 -4
+ Misses 37966 37964 -2
Partials 1773 1773 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Fixed Issues (5)Great job! The following issues were fixed in this Pull Request
|
|
Claude finished @eliykat's task —— View job Code Review Complete ✅Tasks
Review FeedbackOverall Assessment: ✅ APPROVE This PR correctly transfers ownership of the Events and EventsProcessor projects from the Admin Console team to the DIRT (Data Insights & Reporting) team. What was reviewed:
✅ Correct Implementation:
Summary:The ownership transfer is complete and correct. All relevant source and test directories are included, and the file maintains proper organization and sorting conventions. No issues found. |


🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-28487
📔 Objective
Update code ownership of
EventsandEventsProcessorprojects to the Data Insights and Reporting Team (DIRT), as the new owners of the organization events domain.📸 Screenshots
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:) or similar for great changes:memo:) or ℹ️ (:information_source:) for notes or general info:question:) for questions:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:) for suggestions / improvements:x:) or:warning:) for more significant problems or concerns needing attention:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt:pick:) for minor or nitpick changes