Commit 5a26e9d
committed
fix(scan github): don't print success counts when returning blocking error
Before: on rate-limit / auth abort, the function emitted
"N GitHub repos processed / 0 with supported Manifest files" followed
by logger.fail(...). The success lines implied partial progress even
though we're about to return ok:false, which is confusing output.
Move the success counters past the blocking-error return so they only
print on actual completion.1 parent 627ffc0 commit 5a26e9d
1 file changed
+3
-3
lines changedLines changed: 3 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
148 | 148 | | |
149 | 149 | | |
150 | 150 | | |
151 | | - | |
152 | | - | |
153 | | - | |
154 | 151 | | |
155 | 152 | | |
156 | 153 | | |
157 | 154 | | |
158 | 155 | | |
| 156 | + | |
| 157 | + | |
| 158 | + | |
159 | 159 | | |
160 | 160 | | |
161 | 161 | | |
| |||
0 commit comments