chore: remove web-platform from CODEOWNERS#92
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
shepp-bolt
approved these changes
Jun 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Removes
@BoltApp/web-platformfrom.github/CODEOWNERS. The default owner for all files is now@BoltApp/eng, and the.github/CODEOWNERSfile itself is owned solely by@BoltApp/tech-leads. This reflects the updated team ownership for this repository.Testing
No functional code changes — this only updates GitHub CODEOWNERS routing. Correctness is validated by GitHub parsing the file and assigning the expected reviewers (
@BoltApp/engfor general files,@BoltApp/tech-leadsfor the CODEOWNERS file) on subsequent PRs.Security Review
Important
A security review is required for every PR in this repository to comply with PCI requirements.
Security Impact Summary
No security-sensitive changes. This PR does not touch authentication, authorization, payment flows, user data handling, or external integrations. It only adjusts code review ownership routing.