Skip to main content

​
Where it lives

Open Settings and go to About — last item in the list on the left.
The action palette (⌘P / Ctrl+Shift+P) and the account menu, on the avatar, get you to the same place.

​
What the screen shows

The commit is the field that settles most bug reports. The version number does not move between releases: every build made during the 0.3.0 cycle calls itself 0.3.0. The commit is what tells them apart — and if you built from source, it is the only thing that identifies what you have on your machine.
If TYBA was built from a source tarball with no git history, Commit and Commit date show —. That is not an error: that build has no such information to give.

​
Copy diagnostics

The Copy diagnostics button puts a ready-to-paste block on your clipboard:
That is all it carries. No folder paths, no local account name, no repository or branch names, no open sessions, no environment variables. The block is built to be pasted into a public issue without you having to read it line by line first.

​
When a new version is out

The version card swaps its bottom line for Version X is out and a See what changed button appears, opening the changelog in your browser.
TYBA never downloads or installs an update on its own. It tells you and opens the changelog; downloading the new version is your call, on the download page.
The last card takes you to the repository, the documentation, the changelog and the license — TYBA is Apache-2.0.

​
See also