Report token scan results in tables
This commit is contained in:
+12
-5
@@ -276,13 +276,20 @@ Przelaczniki:
|
||||
Typowy wynik:
|
||||
|
||||
```text
|
||||
repo_root<TAB>...
|
||||
scanned<TAB>1
|
||||
added<TAB>1
|
||||
servers<TAB>1
|
||||
token_path<TAB>...
|
||||
summary
|
||||
repo_root<TAB>remotes<TAB>urls<TAB>scanned<TAB>auth_urls<TAB>plain_urls<TAB>unsupported_urls<TAB>found<TAB>added<TAB>servers<TAB>token_path
|
||||
...<TAB>1<TAB>1<TAB>1<TAB>1<TAB>0<TAB>0<TAB>1<TAB>1<TAB>1<TAB>...
|
||||
|
||||
remotes
|
||||
remote<TAB>endpoint<TAB>type<TAB>url_kind<TAB>user<TAB>result
|
||||
r1<TAB>http://77.90.8.171:3001<TAB>gitea<TAB>auth<TAB>u1<TAB>added
|
||||
```
|
||||
|
||||
Jesli remote istnieje, ale ma URL bez `LOGIN:TOKEN@`, wynik bedzie mial
|
||||
`plain_urls=1`, `auth_urls=0`, `found=0`, `added=0`, a w tabeli `remotes`
|
||||
pojawi sie `url_kind=plain` i `result=no_credentials`. To znaczy, ze `scan`
|
||||
sprawdzil remote, ale nie znalazl sekretu do zapisania.
|
||||
|
||||
Przyklad:
|
||||
|
||||
```bash
|
||||
|
||||
Reference in New Issue
Block a user