-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow the wakatime api key to be persisted via settings sync #283
Comments
I was about to create the very same issue. I only work in devcontainer (for a clean python env) and I have to re-enter the api key at every mod or new container image. If we can have it in the user/settings that will save me time. |
I use GitHub codespace Whenever I create new codespace I have to enter API key again and again which is just time wasting! |
I'll work on a PR for this. How about a checkbox to enable saving to vscode settings instead of the |
+1 |
@alanhamlett How are the works on the PR? |
For those who use Devcontainers, you can bind "runArgs": [
"-v",
"${env:HOME}/.wakatime.cfg:/root/.wakatime.cfg"
], |
Which file is this to be added to? Trying to add it to |
Please check https://containers.dev/implementors/json_reference/#image-specific |
@alanhamlett Is work still being done on a PR? If not I might be able to work on this |
Not yet, so go for it 👍 |
Submitted a PR! |
No description provided.
The text was updated successfully, but these errors were encountered: