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
* feat: add current state
* feat: add current state
* refactor(git.go): remove function and simplify return
* refactor(gui.go): decrease indent for title text
this slightly dedents everything to align properly
* refactor(gui.go): change deprecated methods
* refactor(gui.go): change selected item's prefix indicator
this now matches the other input fields
* refactor: clean up how the configuration is used
it was a real mess before
* feat: add session as statistics field
* refactor(gui.go): remove colons
they kind of don't make sense in the location they're at
* refactor(gui.go): remove filtering
didn't work anyway
* feat: simplify stat display and add options
* docs: describe new configuration options
* feat(main.go): add '-s' flag to just show statistics
* docs(README.md): add note about new '-s' flag
There is an additional `comet.json` file that includes the prefixes and descriptions that I most prefer myself, which can be added to either the root of a repository, to one's home directory as `.comet.json` or to `${XDG_CONFIG_HOME}/cometary/config.json`. Omitting this means that the same defaults are used as in the original.
44
44
45
-
- To adjust the character limit of the scope, add the key `scopeInputCharLimit`into the configuration file with the desired limit
46
-
-Omitting the key uses a default value of 16 characters
47
-
- To adjust the character limit of the message, add the key `commitInputCharLimit`into the configuration file with the desired limit
48
-
-Omitting the key uses a default value of 100 characters
49
-
- To adjust the total limit of characters in the *resulting* commit message, add the key `totalInputCharLimit`into the configuration file with the desired limit
45
+
- To adjust the character limit of the scope, add the key `scopeInputCharLimit` with the desired limit
46
+
-Default: 16
47
+
- To adjust the character limit of the message, add the key `commitInputCharLimit` with the desired limit
48
+
-Default: 100
49
+
- To adjust the total limit of characters in the *resulting* commit message, add the key `totalInputCharLimit` with the desired limit
50
50
- Adding this key overrides scope- and message-specific limits
51
-
- To adjust the order of the scope completion values (i.e. longer or shorter strings first), then add the key `scopeOrderCompletion` into the configuration file with either `ascending` or `descending` as the values
52
-
- Omitting the key uses a default order of descending
51
+
- To adjust the order of the scope completion values (i.e. longer or shorter strings first), add the key `scopeOrderCompletion` with either `"ascending"` or `"descending"`
52
+
- Default: `"descending"`
53
+
- To enable the storing of runtime statistics, add the key `storeRuntime` with the value `true`
54
+
- Default: `false`
55
+
- This will create a `stats.json` file next to the configuration file with aggregated statistics across days, weeks, months, and years
56
+
- To show the session runtime statistics after each commit, add the key `showRuntime` with the value `true`
57
+
- Default: `false`
58
+
- This will show `> Session: N seconds` after the commit was successful
59
+
- To show the all-time runtime statistics after each commit, add the key `showStats` with the value `true`
60
+
- Default: `false`
61
+
- To just show the all-time runtime statistics and quit the program, run the program with the `-s` flag
62
+
- To adjust the format of the statistics from seconds to hours or minutes, add the key `showStatsFormat` with either `"minutes"` or `"hours"`
63
+
- Default: `"seconds"`
64
+
- To always show session runtime statistics as seconds but keep everything else as defined by `showStatsFormat`, add the key `sessionStatAsSeconds` with the value `true`
65
+
- Default: `false`
53
66
54
67
There is also a `-m` flag that takes a string that will be used as the basis for a search among all commit messages. For example: if you're committing something of a chore and always just use the message "update dependencies", you can do `cometary -m update` (use quotation marks if argument to `-m` includes spaces) and Cometary will populate the list of possible messages with those that include "update", which can then be cycled through with the Tab key. This is similar to the search you could make with `git log --grep="update"`.
0 commit comments