Misc. minor dev #181
Open
Misc. minor dev #181
Conversation
This file contains 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
Codecov Report
@@ Coverage Diff @@
## master #181 +/- ##
==========================================
- Coverage 82.83% 82.78% -0.05%
==========================================
Files 184 184
Lines 10557 10557
Branches 1660 1660
==========================================
- Hits 8745 8740 -5
- Misses 1125 1126 +1
- Partials 687 691 +4
Continue to review full report at Codecov.
|
muffato
force-pushed
the
feature/misc_dev
branch
2 times, most recently
from
bba20b0
to
990dffa
Compare
The view is not yet enabled and will require matching schema patches.
muffato
force-pushed
the
feature/misc_dev
branch
from
990dffa
to
5bca20e
Compare
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.
Use case
A collection of minor changes I have locally: bugfixes and new features
Description
progress, which shows which analysis created each job. The view is not enabled yet because I didn't want to create a new schema version just for that right now. If you want to keep the view, a patch can be added now, or later, bundled with another schema change so that users of themasterbranch don't see too many changes.Possible Drawbacks
None
Testing
Have you added/modified unit tests to test the changes?
If so, do the tests pass/fail?
Have you run the entire test suite and no regression was detected?