You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to increase the accuracy of the time tracked with giTrack I have an idea of using watchdog to monitor changes of files inside the Git repo and if for some configured time, no activity would be detected then the time tracking would be paused.
There might be thou different reasons for this inactivity: doing research, being on meetings, debugging etc. Therefore, I am more inclining to not completely discard the tracking information, but instead store them locally and when activity is resumed, ask the user if the break should be count as tracked time. There should be quiet extensive configuration around this, so everybody could configure it to its need.
This will require to implement a daemon that will run separately in the background and track the activity.
The text was updated successfully, but these errors were encountered:
In order to increase the accuracy of the time tracked with giTrack I have an idea of using watchdog to monitor changes of files inside the Git repo and if for some configured time, no activity would be detected then the time tracking would be paused.
There might be thou different reasons for this inactivity: doing research, being on meetings, debugging etc. Therefore, I am more inclining to not completely discard the tracking information, but instead store them locally and when activity is resumed, ask the user if the break should be count as tracked time. There should be quiet extensive configuration around this, so everybody could configure it to its need.
This will require to implement a daemon that will run separately in the background and track the activity.
The text was updated successfully, but these errors were encountered: