timetracker VS timetrace

This was my plan when I made this time tracker. Just start it once and it tracks which window you are on. Works only for Windows right now though, any help appreciated.

Timetrace (https://github.com/dominikbraun/timetrace) is an excellent cli tool for keeping track of time spent on various projects. However, if you are working on a restricted corporate network that does not permit the installation of software, it is difficult to use, especially if said network also restricts outgoing connections so that you cannot ssh to a machine which has timetrace installed.

pkg i golang python git mkdir git && cd git git clone https://github.com/dominikbraun/timetrace.git cd timetrace go build . ./timetrace --help

In my new job, I'm not required to track my working time anymore. However, since I'm getting paid for working 40 hours a week, I decided to track it myself and wrote a CLI tool: timetrace.

In my new job, I'm not required to track my working time anymore. However, since I'm getting paid for working 40 hours a week, I decided to track it myself and wrote a CLI tool: timetrace.

Thanks! Yes, there already is the completion directory serving as a scaffold for autocompletion, and there's an existing issue in work: https://github.com/dominikbraun/timetrace/issues/135

It is also possible to print the tracking status in your custom format using the --format flag. There is a pre-defined set of variables. For example, {project} will be replaced with the name of the current project.

Don't have the time for mentoring, but I recently started a project with several open issues - most of them aren't too hard to solve and rather beginner-friendly. It could be a gentle introduction to Go.

So I recently started my new job where my working time isn't tracked anymore. However, I decided to track it myself and created a simple CLI: timetrace