Blog: add update to Security CI incident#7658
Conversation
Co-Authored-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Co-Authored-By: Richard Lau <rlau@redhat.com> Co-Authored-By: Matteo Collina <matteo.collina@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
FYI for Node.js Website Team (Unrelated to contents of this PR): |
|
Lighthouse Results
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7658 +/- ##
=======================================
Coverage ? 74.61%
=======================================
Files ? 96
Lines ? 7689
Branches ? 192
=======================================
Hits ? 5737
Misses ? 1950
Partials ? 2 ☔ View full report in Codecov by Sentry. |
|
FYI, I might not be available next week. Feel free to merge this PR on Monday. |
mcollina
left a comment
There was a problem hiding this comment.
I need to send some edit, will do asap.
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com> Signed-off-by: Matteo Collina <matteo.collina@gmail.com>
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com> Signed-off-by: Matteo Collina <matteo.collina@gmail.com>
Signed-off-by: Matteo Collina <matteo.collina@gmail.com>
|
@nodejs/nodejs-website can someone help me sorting out the linting here? This is exactly like we want it. |
Signed-off-by: Matteo Collina <matteo.collina@gmail.com>
Signed-off-by: Matteo Collina <matteo.collina@gmail.com>
You need to run
What does |
Note that the content is correct. |
|
Can you run prettier on the content? The ESLint issue is just a warning, and wouldn't fail the quality checks |
cc: @nodejs/tsc