Repository navigation
chore: rename the repo to token-usage-dashboard - #23
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Category
Refactor (well, a rename)
Overview
The repo, the CLI file, the systemd unit, the Docker image and the page title all say
token-usage-dashboardnow, so they match the npm package andnpx token-usage-dashboard. Theaiusagecommand and theAIUSAGE_*variables stay as they are.The default database moves to
~/.local/share/token-usage-dashboard, but if there's already a folder at the oldai-usage-dashboardpath it keeps using that, so nobodys history goes missing.Issue Number
None
Additional Info
Docker users will want
notaflightrisk/token-usage-dashboardonce the next tag pushes it. The compose volume istoken-usagenow, so anyone on the old compose file should keep theirai-usagevolume or copy the data over.Ran format, types, tests and build, and started the CLI against an empty data dir and one with the old folder in it. It picked the right one both times.
Some AI was use when making this