-
Notifications
You must be signed in to change notification settings - Fork 60
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 3.0 scratch #403
Feat 3.0 scratch #403
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## feat-3.0 #403 +/- ##
===========================================
Coverage ? 82.54%
===========================================
Files ? 29
Lines ? 1369
Branches ? 145
===========================================
Hits ? 1130
Misses ? 178
Partials ? 61
|
@@ -0,0 +1,3 @@ | |||
-----BEGIN PRIVATE KEY----- |
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.
These are test assets, right? I'm wondering if we could put them in some separate place. I would expect that folder <sub-project>/assets
contains files that are needed for the actual compilation and runtime of the project.
This can be done in a later PR though.
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.
LGTM 👍
patch: | ||
default: | ||
target: auto | ||
threshold: 5% |
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.
we will make it higher value over time ;)
Closes #412