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
+16-4Lines changed: 16 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -22,16 +22,26 @@
22
22
23
23
**Gitlogg** is not a very complex application, but I still made an effort to provide some feedback on what is happening under the hood. Below are some screenshots of dialogs one can expect to see while executing it:
24
24
25
-

26
-
> **Success!**`JSON` parsed, based on **7** different repositories with a total of **7375** commits.
27
-
28
25

29
26
> **Øh nøes!** The path to the folder containing all repositories *does not exist!*
30
27
31
28

32
29
> **Øh nøes!** The path to the folder containing all repositories *exists, but is empty!*
33
30
34
-
## Requirements
31
+

32
+
> **Success!**`JSON` parsed, based on **9** different repositories with a total of **25,537** commits.
33
+
34
+
Note that I've included two huge repos (react & react-native, that have 7,813 & 10,065 commits respectively at the time of this writting) for the sake of demonstration. The resulting parsed `JSON` file has 715,040 lines. All that done in less than 25 seconds.
35
+
36
+
*I have successfully compiled **`470`** repositories at once* (all repos under the organization I work for). Then I got these specs:
37
+
38
+
*`gitlogg.tmp` generated in `154s` (`~2.57mins`)
39
+
*`JSON` output parsed in `2792ms`
40
+
*`JSON` file size: `121,5MB`
41
+
* Commits processed: `118,117`
42
+
* Parsed `JSON` file, lines: `3,307,280`
43
+
44
+
## Requirementss
35
45
36
46
[NodeJS][2] and [BabelJS][3].
37
47
@@ -47,6 +57,7 @@ The output will look like this (first commit for **Font Awesome**):
@@ -84,6 +95,7 @@ The output will look like this (first commit for **Font Awesome**):
84
95
Note that many `git log` fields were not printed here, but that's only because I've commented out some of them in the **gitlogg-parse-json.js** script. All the fields below are available. Fields marked with a `*` are either non-standard or not available as placeholders on `--pretty=format:<string>`:
0 commit comments