Getting help
FAQ
glab, self-managed GitLab, Windows, repository access, and what labdash sends where.
Troubleshooting
Symptom, cause and fix, for the failures that happen in practice.
Diagnostics
doctor, the debug HTTP log, the application log, and what to put in a report.
Terminal support
The matrix: terminal, colour, mouse, clipboard, resize.
Security
Where the token lives, which scopes are requested, and what stays on your machine.
Privacy
What labdash sends and where, what this site records, and where that leaves you under data protection law.
labdash doctor
One command, one paste. It reports whether the settings file was found and is valid, whether a credential is present and unexpired, whether the instance is reachable, the GitLab version, your terminal's capabilities, and which icon set your locale selected.
It never prints a token.
Bug reports
Include the doctor output, what you expected, and what happened. For a rendering problem, the terminal name and version matter most.
If the problem involves a request, add the debug log:
Requests go to a file with Authorization, PRIVATE-TOKEN and JOB-TOKEN redacted before anything reaches the disk. See diagnostics.
Not into a bug report, not into a chat, not "with most of it removed". A partially redacted token is a leaked token. If one reaches a transcript, revoke it at https://<host>/-/user_settings/personal_access_tokens, which takes ten seconds.