-
Notifications
You must be signed in to change notification settings - Fork 509
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add options to import and export database (fixes #1655) #1656
Conversation
Resync repository
chore: update pre-commit config
This reverts commit d78d40e.
…1655)" This reverts commit fe9a71d0497e555a96b0a2eda420ef485ce77a94.
Codecov Report
@@ Coverage Diff @@
## main #1656 +/- ##
==========================================
+ Coverage 78.66% 80.35% +1.68%
==========================================
Files 296 298 +2
Lines 6141 6204 +63
Branches 1002 1009 +7
==========================================
+ Hits 4831 4985 +154
+ Misses 1093 1005 -88
+ Partials 217 214 -3
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might be the most valid use of the "request changes" button ever... but for some reason I'm seeing 0 changes in this PR. I think maybe you overwrote your branch or something?
Ooops. No idea how that happenned but hopefully the correct code is now available. |
My merge of the exploited cves code caused a conflict. I've manually resolved it through the web interface. |
(Flagging so I know to come back after the tests run) |
@anthonyharrison looks like I broke the linting, if you've got a chance to update it. |
@terriko Fixed the linting problem. Ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thank you! This should make moving the db around much safer and significantly more clear for the users who need to do that. I wonder if we could use this to do improve our github caching by having a copy in the repo?
No description provided.