Conversation
Codecov ReportAttention: Patch coverage is
❌ Your project status has failed because the head coverage (74.84%) is below the target coverage (90.00%). You can increase the head coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #611 +/- ##
==========================================
- Coverage 74.87% 74.84% -0.04%
==========================================
Files 173 173
Lines 7902 7906 +4
==========================================
Hits 5917 5917
- Misses 1681 1685 +4
Partials 304 304
🚀 New features to boost your workflow:
|
Contributor
|
I'm desperately wanting this today as my team will have a need to list secrets a lot in the next couple of weeks as we do a minor refactor of our Vela config as we migrate ~120 repos to a new directory layout, among other things. |
plyr4
approved these changes
Jun 10, 2025
Contributor
|
heck yeah good catch, thanks yall |
ecrupper
approved these changes
Jun 10, 2025
Contributor
|
Thank you! |
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.
fixes go-vela/community#1056
avoids issues when you have color output enabled but are sending output to non-terminal. example (typically, the scenario is that you might have color enabled globally):
$ vela --color true view repo --org <org> --repo <repo> --output json | jq -r '.'currently results in:
jq: parse error: Invalid numeric literal at line 1, column 2due to color codes in response. this simple fix in the PR overrides color output in such scenarios so users don't have to manually strip color code prior to working with the data when piping to other utils.