chore: Add team-ai-sme as Dockerfile co-owner - #240
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #240 +/- ##
=======================================
Coverage 59.88% 59.88%
=======================================
Files 15 15
Lines 1199 1199
Branches 253 253
=======================================
Hits 718 718
Misses 405 405
Partials 76 76 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
🤖 Bitwarden Claude Code ReviewOverall Assessment: APPROVE This is a one-line Code Review Details
|
|
@withinfocus are you thinking this should be co-owned, or only under @bitwarden/team-ai-sme? |
|
I think that you should list your team alongside the existing owners for this file, so you can self-manage. |
🎟️ Tracking
No tracking issue; follow-on to #219, which set
@bitwarden/team-ai-smeas this repo's default owner.📔 Objective
We own this repo but hold no review claim on its
**/Dockerfile, so the container image we publish can change without anyone on our team seeing it. Adding us alongside team-appsec and dept-bre leaves both existing gates intact and gives us visibility into the image that ships under our name.