Conversation
Codecov ReportAttention: Patch coverage is
❌ Your patch check has failed because the patch coverage (15.15%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## master #423 +/- ##
==========================================
- Coverage 37.81% 37.72% -0.10%
==========================================
Files 53 53
Lines 4458 4472 +14
==========================================
+ Hits 1686 1687 +1
- Misses 2685 2698 +13
Partials 87 87 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
This pull request is stale because it has been open for 30 days without activity. |
|
keepalive |
e724ff2 to
8180c28
Compare
mbrt
left a comment
There was a problem hiding this comment.
Nice, thanks! I can't immediately see why, but I tested manually, and it looks like gmailctl diff --color=never still colorizes the output. Could you double-check? Maybe I'm missing something.
|
Sorry about that. I fixed it so label diffs respect Also, would you want a |
|
@kpengboy I think this looks good enough, thanks! |
|
Rebased. |
|
Could you please fix the tests? |
|
Fixed the tests. Also, I wrote an alternative version of this PR which supports |
|
@kpengboy I think it's fine to move to the slightly newer (but still unmaintained) version from Just one comment on the branch: I would prefer to keep the The logic of parsing the I hope this makes sense. |
|
This pull request is stale because it has been open for 30 days without activity. |
|
keep alive |
562b789 to
e6fec45
Compare
|
I've chosen to move to the alternative implementation. I moved the |
Whether to colorize the diff output is controlled by a --color flag.
|
Nice job! Thanks @kpengboy! |
This would at least be a partial solution to #371.
I did not add the colorization to the cfgtest output, but I wonder if I should.