feat(git-node): add git node security --apply-patches#1050
Open
aduh95 wants to merge 2 commits into
Open
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1050 +/- ##
==========================================
- Coverage 65.22% 65.21% -0.01%
==========================================
Files 45 45
Lines 6916 6917 +1
==========================================
Hits 4511 4511
- Misses 2405 2406 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
git node security --prepare-local-branchgit node security --apply-patches
RafaelGSS
reviewed
Jun 10, 2026
RafaelGSS
left a comment
Member
There was a problem hiding this comment.
This is missing documentation on git-node
aduh95
commented
Jun 10, 2026
2aa0920 to
ae2a1b6
Compare
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.
I've used that to prepare the 22.22.2 proposal; being able to fetch and apply the patches locally without running the release preparation script is much better UX IMO, and it's nice to be able to do that without needing to change the local config or manually download
vulnerabilities.json.