Automatic, lightweight time tracking for Git projects that captures activity via editor plugins and stores metrics as Git notes.
Git Time Metric (GTM) is a command-line tool that automatically tracks time spent on Git projects without requiring manual timer management. It captures coding activity through editor plugins and stores time metrics locally within the Git repository using Git notes, which can optionally be shared via remote repositories.
Developers and teams who use Git for version control and want to automatically track coding time for productivity analysis, billing, or project management without manual intervention.
GTM integrates seamlessly into existing Git workflows by storing time data as Git notes, making it versioned and portable, and it eliminates the need to manually start/stop timers through automatic background tracking via editor plugins.
Simple, seamless, lightweight time tracking for Git
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Eliminates manual timer management by running via editor plugins, as emphasized in the README's philosophy for seamless, unobtrusive operation.
Stores time metrics as Git notes within the repository, making data versioned and portable, with aliases like pushgtm and fetchgtm for remote sync.
Provides detailed reports via `gtm report` with multiple formats such as summary and timeline-hours, demonstrated in the command examples and screenshots.
Offers plugins for many popular editors including VSCode, Vim, Sublime, and IntelliJ, ensuring wide compatibility and ease of adoption.
Automatic tracking relies entirely on editor plugins; if a plugin is buggy, outdated, or unavailable for your editor, tracking fails without a built-in fallback mechanism.
Time data is stored in Git notes, which aren't pushed by default and require manual syncing commands, making it less suitable for environments where Git isn't the central tool.
GTM is designed solely for automatic tracking via editor activity; it lacks features for manually logging time spent on non-coding tasks, limiting its use for comprehensive time management.