Tracking git branch checked out?

[elliot-nelson]

I just found this project today and have been playing with it, and it might be perfect for me.

The one thing I find missing is: my eventual goal is to be able to take collapsed log files for a day and produce a report (possibly fed through local AI) that can give me a summary of the way I spent my day... without any kind of intentional clocking in-out (no pomodoro stuff).

I think for this I need more than just window titles. "Terminal" and "VSCode" do happen to have their folder opened in the title (and in the case of VSCode, the file as well), which is a good start: but I really need what git branch is checked out in that folder as well.

What I'm hoping is: raw logs minute-by-minute throughout the day, recording window titles, but also if a window title seems to have a folder in it, and that folder contains a .git folder, what branch was checked out during that minute.

Does such a feature exist, or if not, what component should it live in? (I'm potentially interested in contributing it if it would fit into the architecture and the project is still alive.)

[elliot-nelson]

I'm going to add here that another thing incredibly useful would be to tie Copilot conversations to the logs somehow.

Logs in ~/Library/Application Support/Code/User/workspaceStorage/*/chatSessions/*.json, each of which have timestamp properties, could be used to tie to approximate minute.

(Again, exactly how this would happen -- is a different Watcher watching it, or is it part of some existing Watcher, that's what I could use advice on.)

[BelKed]

https://superuser.com/questions/105499/change-terminal-title-in-mac-os-x
https://superuser.com/questions/1612990/how-to-set-terminal-tab-title-to-show-the-current-git-branch-using-zsh

Combining these two questions should allow you to display your current Git branch in the Terminal title, which will then be recorded by ActivityWatch :)

[petrroll]

You could create your own watcher that is somehow configured which folders to watch and reports which branches are current there.

Shouldn't be much work.

A bit harder would be making the finding which folders to watch automatic.

An easier avenue might be extending the VScode watcher. There's link to it from docs about other watchers.