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
Copy file name to clipboardExpand all lines: README.md
+65-2Lines changed: 65 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,9 +3,72 @@
3
3
4
4
Git Time Metrics (GTM) is a tool to automatically track time spent reading and working on code that you store in a Git repository. By installing GTM and using supported plug-ins for your favorite editors, you can immediately realize better insight into how you are spending your time and on what files.
5
5
6
-
###Installation
6
+
# Installation
7
7
8
8
Installing GTM is a two step process. First, it's recommended you install the GTM executable that the plug-in integrates with and then install the Sublime 3 GTM plug-in. Please submit an issue if you have any problems and/or questions.
9
9
10
-
1. Follow the [Getting Started](https://github.com/git-time-metric/gtm/blob/master/README.md) section to install the GTM executable for your operating system.
10
+
1. Follow the [Getting Started](https://github.com/git-time-metric/gtm/blob/master/README.md) section to install the GTM executable for your operating system.
11
11
2. Install the plug-in via [Package Control](https://packagecontrol.io).
12
+
13
+
# Features
14
+
15
+
### Status Bar
16
+
17
+
In the status bar see your total time spent for in-process work (uncommitted).
This can be disabled by setting `gtm_status_bar: false` in gtm.sublime-settings.
22
+
23
+
*Note* - the time shown is based on the file's path and the Git repository it belongs to. You can have several files open that belong to different Git repositories. The status bar will display the time for the current file's Git repository. Also keep in mind, a Git repository must be initialized for time tracking in order to track time.
24
+
25
+
Consult the [README](https://github.com/git-time-metric/gtm/blob/master/README.md) and [Wiki](https://github.com/git-time-metric/gtm/wiki) for more information.
26
+
27
+
### Command Line Inteface
28
+
29
+
Use the command line to report on time logged for your commits.
30
+
31
+
Here are some examples of insights GTM can provide you.
32
+
33
+
**Git commits with time spent**
34
+
35
+
```
36
+
9361c18 Rename packages
37
+
Sun Jun 19 09:56:40 2016 -0500 Michael Schenk 34m 30s
38
+
39
+
341bd77 Vagrant file for testing on Linux
40
+
Sun Jun 19 09:43:47 2016 -0500 Michael Schenk 1h 16m 0s
41
+
42
+
792ba19 Require a 40 char SHA commit hash
43
+
Thu Jun 16 22:28:45 2016 -0500 Michael Schenk 1h 1m 0s
44
+
```
45
+
46
+
**Git commits with detailed time spent by file**
47
+
48
+
```
49
+
b2d16c8 Refactor discovering of paths when recording events
50
+
Thu Jun 16 11:08:47 2016 -0500 Michael Schenk
51
+
52
+
30m 18s [m] event/event.go
53
+
12m 31s [m] event/manager.go
54
+
3m 14s [m] project/project.go
55
+
1m 12s [r] .git/COMMIT_EDITMSG
56
+
1m 0s [r] .git/index
57
+
25s [r] event/manager_test.go
58
+
20s [r] metric/manager.go
59
+
49m 0s
60
+
```
61
+
62
+
**Timeline of time spent by day**
63
+
64
+
```
65
+
0123456789012345678901234
66
+
Fri Jun 24 * 22m 0s
67
+
Sat Jun 25 ** 1h 28m 0s
68
+
Sun Jun 26 **** 3h 28m 0s
69
+
Mon Jun 27 * 4m 0s
70
+
Tue Jun 28 ** 1h 36m 0s
71
+
6h 58m 0s
72
+
```
73
+
74
+
Consult the [README](https://github.com/git-time-metric/gtm/blob/master/README.md) and [Wiki](https://github.com/git-time-metric/gtm/wiki) for more information.
0 commit comments