Add CODEOWNER for vulnerability blog post#8967
Conversation
#8966 should be covered by releasers too? Signed-off-by: Brian Muenzenmeyer <brian.muenzenmeyer@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PR SummaryLow Risk Overview Vulnerability disclosure posts under that path will now automatically request releaser review on PRs. Reviewed by Cursor Bugbot for commit 57fe250. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
Pull request overview
Adds an explicit CODEOWNERS rule so changes to the vulnerability blog section request review from the Node.js releasers team, aligning it with other release-related blog categories.
Changes:
- Add
apps/site/pages/en/blog/vulnerabilityownership to@nodejs/releasersin.github/CODEOWNERS.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8967 +/- ##
==========================================
- Coverage 75.70% 75.68% -0.03%
==========================================
Files 102 102
Lines 8676 8676
Branches 321 322 +1
==========================================
- Hits 6568 6566 -2
- Misses 2105 2107 +2
Partials 3 3 ☔ View full report in Codecov by Harness. |
#8966 should be covered by releasers too?
Description
The website team is seeking more ergonomic governance of changes like this. Releasers reserve the right to forgo formal review processes, this still feels appropriate for things like #8954 etc
Validation
Related Issues
Check List
pnpm formatto ensure the code follows the style guide.pnpm testto check if all tests are passing.pnpm buildto check if the website builds without errors.